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] 2 3 ... 17
Performance will vary greatly based on OS, data, how the data is accessed etc. It is impossible to know what your performance difference will be.

I would suggest creating a copy of some data and encrypting it and running some tests if you want to know what the difference will be.

“REQUIRED FOR OPEN AND ON DATA”  - This means you always need a password to open the file and the file contents are stored encrypted in the file. So if someone were to open a file in a text editor they could not scrape any useful data out of it.

“REQUIRED FOR WRITE AND ON DATA." - This means you can OPEN INPUT the file in PxPlus without a password, allowing you to read it without a password. To do a standard OPEN on the file in PxPlus you need to specify a password, the standard OPEN allowing you to read and write to the file. Also the file contents are stored encrypted in the file. So if someone were to open a file in a text editor they could not scrape any useful data out of it.

Usually you will just want to use “REQUIRED FOR OPEN AND ON DATA” for the more complete security.

As for legacy native encryption vs industry standard encryption performance. Our testing found they performed very similarly. I would strongly recommend using the industry standard  encryption for the better security and ability to have longer passwords. The limitation of only 8 character long passwords for the legacy encryption limits its strength.

ODBC / Re: ODBC Views Issue
« on: May 02, 2023, 08:18:40 AM »
Excellent, I am glad you were able to get it working.

ODBC / Re: ODBC Views Issue
« on: April 28, 2023, 12:27:08 PM »
In the more recent version of the PxPlus SQL ODBC Driver and PxPlus SQL Server the path to views DLL/Lib is configured on the server side not the client side. On the server you can point it to any directory path to a directory that contains the pvxwin32.dll. A network path can work but it may be less reliable if the connection is not very stable and fast.

If you are using an older version you may be able to resolve your issue by updating to the latest as many bugs have been fixed over the years.

ODBC / Re: ODBC Views Issue
« on: April 26, 2023, 08:59:19 AM »
I would check that the data in the tables in the problem view fits within the field size defined in the data dictionary. I think I have seen errors like this before when the data in the table that makes up the view is incorrect.

ODBC / Re: ODBC Views Issue
« on: April 26, 2023, 08:03:55 AM »
Views require special configuration so the ODBC driver knows where it can find the DLL to process the view.

Check out this answer in the PxPlus ODBC FAQ: https://manual.pvxplus.com/?odbc/odbc_faq.htm#Mark6

Hopefully that will help.

Note that the PxPlus where the pvxwin32.dll is found needs to be properly activated for this to work.

ODBC / Re: Dictionary definition for dates in YYMMDD format
« on: March 06, 2023, 09:42:40 AM »
You can define the class as DATE-YYMMDD


This will tell the ODBC driver that the field is a date. From excel you can just ignore the format the date is stored in and use the standard SQL date format YYYY-MM-DD in your SQL query.

So if using the query wizard to get data you can just define a filter for that field <= 2022-06-30.

Or if you use the Microsoft Query you can edit the SQL query directly it would be something like

SELECT * FROM myTable WHERE dateFld <= '2022-06-30'

ODBC / Re: ODBC Date Issue
« on: March 06, 2023, 09:28:23 AM »
The PxPlus SQL ODBC driver supports that date class.

When using SQL though you use the SQL date format (YYYY-MM-DD) the driver does the conversion to how the date is stored in your file. So assuming your data dictionary has set the date class for the field correctly if you do a SQL query like

SELECT * FROM myTable WHERE datefld > '2022-09-01'

you should get what you want.

ODBC / Re: ODBC Date Issue
« on: March 03, 2023, 03:26:31 PM »
To answer your question I am only referring to the WHERE clause.

and the format is YYYY-MM-DD not YYYY/MM/DD dashes and not forward slashes.

ODBC / Re: ODBC Date Issue
« on: March 03, 2023, 02:18:44 PM »
I am able to filter based on a date field in Excel just fine.

As I said earlier the issue may be the date format you are trying to use. The ODBC expects YYYY-MM-DD for date fields.

ODBC / Re: ODBC Date Issue
« on: March 03, 2023, 09:14:08 AM »
I can see a few possible issues:

1. your WHERE clause is not using the correct field name. It should be Order_Date not Order Date. You need the underscore and not a space. Then again maybe that is just an issue with typing it out for the forum but it is in both your examples so it could be the issue.

2. Use single quote not double quote.

2. If Order_date is defined with a DATE class you may need to use the date format yyyy-mm-dd in your SQL query.

WHERE Order_Date > '2022-09-01'

ODBC / Re: Operator error
« on: February 28, 2023, 08:29:10 AM »
You must be using a older version of the ODBC driver. Since version 6 (released 2016) of the PxPlus SQL ODBC driver it supports dates with or without the date being escaped.

ODBC / Re: DATE field query
« on: February 28, 2023, 08:26:34 AM »
You can use a Scalar functions (https://manual.pvxplus.com/?odbc/using_odbc_driver/scalar_functions.htm) to modify what is returned by the select:

SELECT LEFT(SO_SalesOrderHeader.OrderDate, POSITION(" " IN SO_SalesOrderHeader.OrderDate) - 1) From myTable

ODBC / Re: Views names showing up, but no data
« on: February 24, 2023, 09:09:06 AM »
The ViewLib= setting should be to the directory where you can find libpvx.so file. So if your PxPlus is installed at /opt/myapp and the libpvx.so is /opt/myapp/libpvx.so then the ViewLib= configuration setting should be ViewLib=/opt/myapp

Another issue could be the activation/license of the PxPlus where we are using the view library from is not active. Views won't work if the PxPlus where the view lib is from is expired or has no activation.

PxPlus products do not automatically update so something else on the system must have changed. If you can figure out what changed that will help identify the issue.

Maybe the activation expired?
Maybe someone made a configuration change and moved files or changed permissions etc?
New security or antivirus software/rules preventing something from working?

Language / Re: DD numeric definition for SQL validation
« on: February 15, 2023, 02:21:38 PM »
I also tried 55.12999 and it becomes 55.13 in the database so SQL Server is rounding to the 2 decimal places.

Pages: [1] 2 3 ... 17