How Elliott 8.6 Works with Different Versions of the PSQL ADO.NET Client

How Elliott 8.6 Works with Different Versions of the PSQL ADO.NET Client

Release Date: 11/4/2022
Version: 8.6 & Up

Elliott V8.6 starts to use PSQL relational operations.  Both Report Desk & PowerSearch features rely on the PSQL relational engine. To use these features, you should refer to the following KB article to set up the proper databases:  

Elliott 8.6 will work with both PSQL 15 and 13 database servers. You should have the workstations installed with the corresponding PSQL 15 or 13 clients.  Our Report Desk & PowerSearch will work with the PSQL ADO.NET clients that come with PSQL 15 or 13. The physical file name of this client is:
    Pervasive.Data.SqlClient.dll
The versions of this client that come with PSQL 15 are 4.5 and 4.4. The versions of this client that come with PSQL 13 are 4.3 and 4.2. In Elliott 8.6 relational operations, the system will attempt to load the 4.5 client from GAC first.  If 4.5 does not exist, it will try to load 4.4, then 4.3, and lastly 4.2 ADO.NET client. If none of them exist, then the operation will fail.

Keep in mind that the 4.2 ADO.NET client (which comes with PSQL 12 and 13) has the limitation of a  maximum field size of 64K.  The standard Elliott Report Desk definition does not have any report that uses a  field size that exceeds 64K.  But if you should customize a Report Desk report, in some rare situations it is possible you may exceed the maximum 64K size.  The early version of ADO.NET 4.3 client (which comes with PSQL 13) also has this limitation.  It is patched later with v4.3.0.9811 (on 5/6/2019) to remove this 64K field size restriction.  Therefore, if you are on the PSQL 13 client, you may want to install the latest release which has this patch.

Please do not copy Pervasive.Data.SqlClient.dll to the BIN86 folder since that will have no benefit and in many cases it may crash Report Desk. To be more specific: 
  • If the GAC has a newer or the same version of PSQL ADO.NET client as the BIN86 folder has, then it is OK with the Report Writer component to continue functioning. 
  • If the GAC has an older version of PSQL ADO.NET client than the BIN86 folder, then it will fail. 
For this reason, you should not copy Pervasive.Data.SqlClient.dll to the Elliott BIN86 folder.

EMK

    • Related Articles

    • Elliott 8.6 to Distribute 4.4 PSQL Entity Framework Client

      Release Date: 11/2/2022 Version: 8.6 & Up In Elliott 8.6, we distribute PSQL 4.4 Entity Framework Client for Avalara interface (national sales tax collection). You can expect to see the following DLL file in the Elliott BIN86 folder: ...

    • A Case Where PSQL 13 Client Is Not Compatible with PSQL 15 Server

      Release Date: 02/04/2025 Version: 8.6 Do Users Need to Upgrade to PSQL 15 Client When Upgrading PSQL Server? We were often asked in the past if our users should upgrade their PSQL 13 client when they upgrade to the PSQL 15 server. In our past ...

    • How Can I Tell How Many Users Are Using PSQL?

      Release Date: 02/08/2024 Versions: PSQL 13 and Up If you suspect you are running out of PSQL licenses or just want to know how many users are using PSQL, Actian has a utility that provides that information: Monitor. PSQL Monitor utility provides open ...

    • Elliott V7.3 Release Notes: What's New Since Elliott V7.2

      What’s New Since Elliott V7.2 Customer Relationship Management (CRM) CRM and beyond The center of Elliott’s Customer Relationship Management is eContact. eContact is an extension to the Customer database, as well as Vendor, Employee, Salesman, Sales ...

    • Elliott 8.6 Requirements and Features Compatibility

      Release Date: 11/08/2022 Version: 8.6 Introduction Unlike prior versions, Elliott 8.6 starts using the PSQL relational database engine to support features like Report Desk, PowerSearch, and Avalara. If you are thinking of using Elliott 8.6, this ...