PxPlus User Forum

Twitter Twitter Twitter

Recent Posts

Pages: 1 2 [3] 4 5 ... 10
Wish List / Re: XML -> JSON CVS Translator
« Last post by Peter.Higgins on October 15, 2019, 11:51:59 AM »
Hi Josh,
Enjoyed meeting you at Direxions!

Since JSON is a data format similar to csv rather than a document format like xml, I suspect you will still have to modify the original programs for individual nodes.

I suggest making a simple object to return the JSON string when passed a node object using similar logic I use to import XML straight to data IOLISTs.

 VIA tmp$=trn'node(n)'value$
Registration and Setup / Missing files
« Last post by Gilles on October 15, 2019, 10:32:09 AM »

libhpls.so and libhpls.a are missing in the tarball pxp1610-0000-U16-64.taz at the download center.
These two files are in all others V16.10 tarball for Ubuntu

ODBC / Re: Was ODBC included in PxPlus Rev 8 Professional?
« Last post by Ned L on October 15, 2019, 10:30:23 AM »
Devon -
Thank you for your prompt reply!
Thin Client/WindX / Most Common Setup
« Last post by Jeffrey Ferreira on October 15, 2019, 10:03:39 AM »
Hello List,

I have a question re: Common setup environments for Non-Web pxplus.
are people running the pxplus "application server" on a linux machine and then running windx to connect to that "Application Server"
i'm just curious what is the most common setup out there.

we are running rdp to a windows server...(and i dont think that is what most developers are doing)


Programming / Re: tiny font in *browser
« Last post by Thomas Bock on October 11, 2019, 10:09:05 AM »
Oops, that is due to an incorrect V14 installation.
Programming / tiny font in *browser
« Last post by Thomas Bock on October 11, 2019, 10:01:56 AM »
We create simple HTML-files and let them display in the *browser control.
The contents are as simple as: <html><p>Test Test Test</p></html>
The control uses a very very tiny font, which makes text unreadable.
Is it necessary to use <font> or is it possible to adjust the standard font size for the control somehow?
ODBC / Re: Was ODBC included in PxPlus Rev 8 Professional?
« Last post by Devon Austen on October 10, 2019, 04:51:16 PM »
The earliest version of the PxPlus ODBC driver requires PxPlus version 10 license or higher.

To use ODBC with earlier versions of PxPlus/ProvideX requires using the Sage ProvideX ODBC driver. I know the version 4.21 of that driver requires PxPlus/ProvideX version 9 license or higher. So you would have to use a version earlier then that but as to how the licensing works exactly I do not know. I would try maybe the 4.10 version and see if that works.

It is also possible that the older ODBC no longer works on newer Windows so you will just have to try it and see what works. If you have issues your only option would be to purchase a new license so you can use the newer versions of the ODBC driver.
ODBC / Was ODBC included in PxPlus Rev 8 Professional?
« Last post by Ned L on October 10, 2019, 02:51:54 PM »
Was support for ODBC included in Rev 8 Professional?

I have a client running PxPlus Rev 8 Professional on a Redhat Linux system
There don't seem to be any pvx OBDC drivers installed, perhaps because they didn't need them when the system was originally installed.
Now I'd like to be able to access their pxplus data files using SQL from windows.
Can this be done?  Or do I need to buy newer pxplus licensed for each Windows user that would want to run SQL?

Thanks in advance for your assistance.

Ned Lee, AMS Software
Programming / Re: Mail crash
« Last post by Mike King on October 10, 2019, 11:07:26 AM »
We don't tend to use audiodev.dll in the Get File Box logic.  That DLL is part of the Windows services that handle your audio driver.

It should be mentioned though that a quick search on the Internet turns up a warning that some viruses use this DLL name to disguise themselves.


You may want to check your system for viruses.
Language / Re: Error 49
« Last post by Jeff Wilder on October 10, 2019, 09:53:42 AM »
I also found that if the line contains a function or another conditional, it passes without error.

For example, these work in the program above:
Code: [Select]
0070 IF STP(V$) LIKE R$ THEN PRINT "true" ELSE PRINT "false"
Code: [Select]
0070 IF NUL(V$) OR V$ LIKE R$ THEN PRINT "true" ELSE PRINT "false"
Pages: 1 2 [3] 4 5 ... 10