-
The PSQL installation is designed to allow OEM partners to embed the installation with their own application installations (such as Sage 50). In order to allow the most flexibility, the installation is designed to allow the OEM partner to control the size of the PSQL installation by choosing to leave out optional CAB files provided ...
-
Agreed, a change request has previously been submitted asking for the information displayed by the various help-->about menu options to be updated to always include the PSQL product version (in addition to the file version of the PSQL application/utility being used).
-
If you use any of the numerous help-->about menu options available from the various PSQL utilities/applications, they will show you the file version information for the application/utility you are running and not the product version of PSQL. The registry location mentioned previously is a better place to look, but even that can be ...
-
The OP indicated he was using 3.5 provider so my last post was meant to confirm that the 3.5 provider SDK has been updated [to include integration with Visual Studio 2012].
The 3.5 provider works with the initial Entity Framework release (included in .NET 3.5 SP1).
Per the What Is New in Pervasive PSQL guide, "The Data Provider 4.0 ...
-
Yes, the updated ADO.NET 3.5 SDK installation is now available on the Pervasive download page at http://www.pervasivedb.com/psqlv11/pages/default.aspx. I'll ask the webmaster to add a "posted on" date for each SDK download to make it easier to determine when an SDK has been updated in the future.
-
Note that for some reason Microsoft chose to name the binary for BOTH the same (odbcad32.exe). So, you can't just go by file name when launching the ODBC Administrator utilities on 64-bit Windows.
-
This error indicates a problem where the CAB file in question is corrupt. This can sometimes occur during a bad download or if you've copied the install files to a new location and mixed CAB files from different versions of PSQL (such as copying the EXE/MSI from PSQL v11 SP1 while the CAB file comes from PSQL v11 SP2). ...
-
Have downloaded and installed the PSQL ADO.NET 3.2 Provider SDK from Pervasive's web site yet (under the SDK section at http://www.pervasivedb.com/psqlv11/Pages/Default.aspx)? Note the ADO.NET 3.2 Provider SDK does not currently integrate with Visual Studio 2012. An update should be available sometime after PSQL v11 SP3 ships.
-
32-bit or 64-bit PSQL 11.20.016 Server Engine?
32-bit or 64-bit Windows? Windows Server? Windows version?
-
You'll want to use the PSQL ADO.NET Provider to connect. Download and install the ADO.NET Provider SDK on your development system (from http://www.pervasivedb.com/ under the page for the version of PSQL you are using). The SDK contains sample projects and templates for connecting to PSQL databases via C# and VB.Net.