PxPlus User Forum

Twitter Twitter Twitter

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.


Messages - Devon Austen

Pages: 1 ... 4 5 [6] 7 8 ... 19
76
Wish List / Re: query version of ODBC-driver
« on: March 04, 2022, 08:35:23 AM »
The SQLGetInfo call is a Windows API call and not a SQL query. Usually the application that implements a ODBC interface will use the SQLGetInfo call to get information about the ODBC driver to present to the user.

If you are writing your own ODBC client application you can use SQLGetInfo. If you are using an existing ODBC client application like SQL Server or Excel etc, you have to look if they provide you the driver version information (which it would get from our driver via the SQLGetInfo call).

What application are you using to access ODBC?

77
Wish List / Re: query version of ODBC-driver
« on: March 03, 2022, 10:57:55 AM »
Using the pxpsql command line client with --version will return the version.

pxpsql --version

You can also run the PxPlus Sql Server with a --version to get it's version

pxpsqlsvr --version

If on Windows you can hover over the pxpsqlodbc.dll or pxpsqlsvr.exe file to see the version. In this case it will look like 7.0.3.0 for 7.00.0003

On Windows you can also see the ODBC driver version in the Data Source Administrator window. Open a PxPlus ODBC DSN and go to the about tab. Before you create a DSN the ODBC version will appear beside the name of the driver as well.

For the PxPlus SQL Server you can open the pxpsconf.exe config app and go to about to see the version as well.

The version in these programs appears as 7.00.0003.

An ODBC client application can also query the version number using a SQLGetInfo call with the SQL_DBMS_VER property.

Does any of that get you what you want or are you looking for something different?

78
Language / Re: Convert PxPlus File to CSV
« on: March 01, 2022, 09:25:31 AM »
If your customers don't have a pro license and therefore no ODBC then yes a tool like this may be useful.

If your customer does have ODBC an architecture mismatch should never be an issue. If you are using a 32-bit Excel then install the 32-bit ODBC driver, if you are using the 64-bit Excel use the 64-bit ODBC driver. The architecture of your PxPlus does not matter to the ODBC driver, so you can have a 32-bit PxPlus with a 64-bit ODBC driver and that will work and vice-versa.

79
Language / Re: Convert PxPlus File to CSV
« on: March 01, 2022, 08:56:07 AM »
Hi Jeff,

I don't believe there is any utility to convert a PxPlus Keyed file to a CSV file.

It should be fairly straight forward to code yourself though with the benefit of giving you full control over how it works.

80
ODBC / Re: ODBC / Linked Server
« on: February 08, 2022, 11:05:40 AM »
No that won't work.

The compatibility table works both ways.

You need at least a 6.10 server but since you have to upgrade you might as well use 7.00.0003.

81
ODBC / Re: ODBC / Linked Server
« on: February 08, 2022, 10:38:59 AM »
No version 5.20 can't talk with a version 7.00 server. There have been protocol changes that break compatibility. We try our best to keep things as compatible as possible but some features and bug fixes required us to change the protocol the client and server communicate with.

For details on which version is compatible with which please see: https://manual.pvxplus.com/?odbc/odbc_faq.htm#Mark10

82
ODBC / Re: ODBC / Linked Server
« on: February 08, 2022, 10:23:53 AM »
There is no version 3.50 of the 64-bit PxPlus ODBC driver. The first version to have a 64-bit version is 5.00.0000.

I am not to sure what software you are running or how you are getting the version number but 3.50 and 64-bit can't be correct for the PxPlus ODBC driver.

As for SQL Server Support we have made several changes to better support SQL Server in more recent versions of the PxPlus ODBC driver and I would recommend using the latest version 7.00.0003 which you can find on our downloads site. Note that you need an activation compatible with PxPlus 2019 (V16) to run the PxPlus ODBC 7.00.0003.

83
ODBC / Re: Getting a View to Show ODBC
« on: January 21, 2022, 02:22:22 PM »
From the docs: https://manual.pvxplus.com/PXPLUS/odbc/configuration_procedures/odbc_driver_configuration_windows.htm

Path to Views DLL
   
Path to pvxwin32.dll (Windows) or libpvx.so (UNIX/Linux). This is required by the PxPlus SQL ODBC Driver in order to use the Views system (PxPlus Version 5.10 or later).

The pvxwin32.dll is found in the PxPlus Install directory so an example value of the this field would be

C:\PVX Plus Technologies\PxPlus 2021 Upd 2\

we want the directory where it is found and not the [path to the DLL. So don't put the dll name in just the dir.

84
Programming / Re: Google Sheet Objects
« on: January 20, 2022, 08:33:18 AM »
In your example code you set a active range but then pass in a range (A1:C100) to the write command. In this case the active range will not be used and it will just do the write to the cell range passed into the write method. The write will write to cells A1 to A100, B1 to B100, and C1 to C100. Since your range covers 300 cells your cell_value$ should contain 300 SEP delimited fields. If it contains less than 300 then it will write all the fields given in order and write null to the remaining fields. i.e. If cell_value$ has 140 fields then the first 100 fields get written to cells A1 to A100 the last 40 get written to B1 to B40. B41 to B100 and C1 to C100 get blanks written to it.

Your logic has to keep track of where you want to write to in the spreadsheet. You tell it where to write by either specifying a active range and then doing a write with just cell_value$ or you just pass in the range on each write. If you want to start writing to a new column or row you just change the active range or passed in range to the write call.

DIM data$[1:100]
GOSUB READ_DATA
FOR I=1 TO 10
mySpreadsheet'SetRangeCol(I)
mySpreadsheet'Write(data$)
NEXT

Assuming data$[] has SEP delimited data for 100 rows this will write out 100 rows of data for columns A through J.

85
Nomads / Re: *browser and Ctrl+F
« on: November 05, 2021, 08:25:45 AM »
It appears that the Find in Page feature is not implemented by default in the embedded chromium framework we use to implement *Browser.

I will create a wish list item to add this feature to *browser.

86
Nomads / Re: Spell Check TinyMCE
« on: October 22, 2021, 09:34:36 AM »
This seems to be an issue with the embedded chrome browser we ship with PxPlus 2021. Please create a help desk ticket so we can investigate this issue.

https://helpdesk2.pvxplus.com/open.php

87
Programming / Re: Increased Font Size within pdf file
« on: October 22, 2021, 08:20:04 AM »
To have better control of the alignment maybe you want to use the 'TEXT' mnemonic which allows you to define a rectangle that the text is aligned within

https://manual.pvxplus.com/?mnemonics/text.htm

88
ODBC / Re: ODBC window to small to display all PxPlus data
« on: October 07, 2021, 01:11:18 PM »

89
ODBC / Re: ODBC window to small to display all PxPlus data
« on: October 07, 2021, 12:05:49 PM »
You can try this to see if it fixes the issue.

Install the 64-bit v7 SQL ODBC driver and then download the this file http://www.pvxplus.com/downloads/misc/DSNSetupFontFix.zip and extract the pxpsqlodbc.dll file into the install directory.

This patched file may fix the font issue for you. If it does let us know and we can release the fix as a patch

90
ODBC / Re: ODBC window to small to display all PxPlus data
« on: October 06, 2021, 03:14:02 PM »
Does this happen for all tabs in the PxPlus ODBC DSN setup?

Is the text this large for other applications on your system or does the text here look larger? To me the text looks too large and it looks much smaller on my system. My settings are 100% scaling with the text size slider all the way to the left. My screen resolution is 1920x1080.

The dialog uses the Microsoft San Serif font at a size of 8. Is it possible your system has that font replaced with a larger version of the font?

Pages: 1 ... 4 5 [6] 7 8 ... 19