Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
181
Registration and Setup / Re: SSL libraries on Ubuntu64 bit with PxPlus V10 64 bit
« on: October 18, 2019, 08:37:32 AM »
I believe Ubuntu 18 uses OpenSSL 1.1.0 which is not compatible with PxPlus yet (Will be support in PxPlus 2020). You would need to install a 32-bit version of OpenSSL 1.0.2 for PxPlus to work on this OS.
182
ODBC / Re: Was ODBC included in PxPlus Rev 8 Professional?
« 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.
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.
183
Programming / Re: locale settings in chromium browser
« on: August 29, 2019, 11:03:47 AM »
I would suspect that versions before 2019 (v16) would always treat the locale as US since it was not until 2019 that we implemented multi-language support for the embedded browser.
I would suggest resolving the installation issues (probably by doing a clean install in a new directory). If you are not getting a popup menu that means that the embedded chromium browser is not running correctly and any test results could be the result of undefined behavior cause by this.
I would suggest resolving the installation issues (probably by doing a clean install in a new directory). If you are not getting a popup menu that means that the embedded chromium browser is not running correctly and any test results could be the result of undefined behavior cause by this.
184
Programming / Re: Question about the end clause of a select / next record loop
« on: August 20, 2019, 04:49:46 PM »
The BEGIN and END on a SELECT are evaluated once at the beginning.
185
Programming / Re: [TCP] open fails, but curl works
« on: August 20, 2019, 10:54:05 AM »
Are you sure they don't exist?
They may just be in a different folder i.e. /lib/, /lib64/oppenssl/, /usr/lib64, or /usr/lib etc
You may be able to figure out where by doing a "which openssl" and then a ldd on the openssl binary.
They may just be in a different folder i.e. /lib/, /lib64/oppenssl/, /usr/lib64, or /usr/lib etc
You may be able to figure out where by doing a "which openssl" and then a ldd on the openssl binary.
186
Programming / Re: disable chromium nrowser popup
« on: August 19, 2019, 08:58:58 AM »
We have tested this here with that setup and everything works fine.
Does the issue happen just for one panel or does it happen for any chromium object?
Maybe the issue is with the WindX Plug-in install. Try doing a fresh install of the plug-in and using that to see if it resolves the issue.
Does the issue happen just for one panel or does it happen for any chromium object?
Maybe the issue is with the WindX Plug-in install. Try doing a fresh install of the plug-in and using that to see if it resolves the issue.
187
Programming / Re: disable chromium nrowser popup
« on: August 16, 2019, 08:49:17 AM »
I have tested here with PxPlus 2017 for the host and Windx Plugin 2017 for the client and I got a popup menu when testing *Browser via nomads or via a DEF OBJECT with a [wdx]/[lcl].
On the WindX client are you running a WindX plug-in or full PxPlus?
What version is the client?
Does the client locales folder have a en-US.pak file?
On the WindX client are you running a WindX plug-in or full PxPlus?
What version is the client?
Does the client locales folder have a en-US.pak file?
188
Programming / Re: disable chromium nrowser popup
« on: August 15, 2019, 09:21:43 AM »
Hi Thomas,
The popup menu should not be empty. If it is empty that means something is likely amiss with your PxPlus install.
1) What version of PxPlus are you using?
2) Are you using an updated PxPlus EXE or the PxPlus EXE that shipped with the PxPlus install?
3) What is the contents of the locale folder under your PxPlus install directory? You should see a bunch of .pak files and you should find one that matches your system language also make sure the en-US.pak is there.
4) If using PxPlus 2019, are you setting BrowserLang in the PxPlus INI file or via 'OPTION' mnemonic? If using PxPlus 2019 and not setting BrowserLanf it defaults to the user OS language. If using earlier versions of PxPlus it always uses English.
Answering the above should help with figuring out the cause of the issue.
There is currently no way to disable the popup menu but I suspect you only want that because it display nothing.
The popup menu should not be empty. If it is empty that means something is likely amiss with your PxPlus install.
1) What version of PxPlus are you using?
2) Are you using an updated PxPlus EXE or the PxPlus EXE that shipped with the PxPlus install?
3) What is the contents of the locale folder under your PxPlus install directory? You should see a bunch of .pak files and you should find one that matches your system language also make sure the en-US.pak is there.
4) If using PxPlus 2019, are you setting BrowserLang in the PxPlus INI file or via 'OPTION' mnemonic? If using PxPlus 2019 and not setting BrowserLanf it defaults to the user OS language. If using earlier versions of PxPlus it always uses English.
Answering the above should help with figuring out the cause of the issue.
There is currently no way to disable the popup menu but I suspect you only want that because it display nothing.
189
Programming / Re: character set option
« on: July 16, 2019, 08:52:26 AM »
After doing the write you can do a KEN(chan) on the channel to see what the SQL was that PxPlus sent to MySQL. If you look at that after the write does that data being sent in the SQL have the accented characters?
If the answer to that is yes then also answer the following question:
If you look at the data in the MySQL table using the MySQL client does it have the accented characters?
If the answer to that is yes then also answer the following question:
If you look at the data in the MySQL table using the MySQL client does it have the accented characters?
190
ODBC / Re: ODBC Ver 6 - 64bit vs 32bit with Division
« on: July 10, 2019, 09:24:16 AM »
OK that was the reason I didn't reproduce the issue.
I tried with a table with 0 in the field and got the crash as described.
This is a bug in the ODBC driver and you will need to create a help desk ticket (http://helpdesk.pvxplus.com/) so we can track and resolve the issue.
I tried with a table with 0 in the field and got the crash as described.
This is a bug in the ODBC driver and you will need to create a help desk ticket (http://helpdesk.pvxplus.com/) so we can track and resolve the issue.
191
ODBC / Re: ODBC Ver 6 - 64bit vs 32bit with Division
« on: July 08, 2019, 04:11:11 PM »
I just tried this here and I do not get any crash. I get back the correct response for the query.
I am testing with one of my own files. Could it be that your file has some odd data in it that it triggering the problem?
I would suggest you create a helpdesk ticket if you want PVX Plus to look further into the crash issue.
I am testing with one of my own files. Could it be that your file has some odd data in it that it triggering the problem?
I would suggest you create a helpdesk ticket if you want PVX Plus to look further into the crash issue.
192
Language / Re: Windx Linux Shell Commands
« on: July 03, 2019, 04:09:51 PM »
If you want to read back the result you can use pipe IO instead i.e.
OPEN (chn)"<cat my_file | grep 'serach string'"
read record (chn) result$
You then can keep doing reads until you get an EOF.
You can use INVOKE, but if you want the result you need to redirect it to a file and read the file.
INVOKE "cat my_file | grep 'serach string' > result"
open (chan)"result"
read record (chn) result$
OPEN (chn)"<cat my_file | grep 'serach string'"
read record (chn) result$
You then can keep doing reads until you get an EOF.
You can use INVOKE, but if you want the result you need to redirect it to a file and read the file.
INVOKE "cat my_file | grep 'serach string' > result"
open (chan)"result"
read record (chn) result$
193
Language / Re: Windx Linux Shell Commands
« on: July 02, 2019, 09:07:33 AM »
The INVOKE directive allows you to pass a command off to the operating system.
INVOKE "cat my_file | grep 'serach string'"
If you want the send the Windows workstation the command prefix with [wdx] or [lcl]
https://manual.pvxplus.com/?directives/invoke.htm
INVOKE "cat my_file | grep 'serach string'"
If you want the send the Windows workstation the command prefix with [wdx] or [lcl]
https://manual.pvxplus.com/?directives/invoke.htm
194
While they only have a 64-bit version of the MySQL server for most recent versions you don't need to install the MySQL server to use the [mysql] interface in PxPlus. You only need to install the MySQL connector/C which can be installed via the MySQL installer as x86 (32-bit). This will install the 32-bit libmysql.dll needed for PxPlus.
195
Thin Client/WindX / Re: Windx Security on Terminal Server
« on: June 17, 2019, 03:43:20 PM »
The documentation is correct it was a feature added in PxPlus 2017 (V14). The original question stated they are using PxPlus 15.10.0001 which is PxPlus 2018 so they should be able to use it.