Using Pervasive.SQL on a 64 bit CPU

Article ID: 080717094532 - Last Review: 18 December 2008 by jasonl - Revision: 2 - Views: 6276


About "Using Pervasive.SQL on a 64 bit CPU"
From the Pervasive web site:

Pervasive.SQL V10 "Summit"
Pervasive PSQL Summit v10 supports both the 32-bit and 64-bit editions running on a supported 64-bit operating system and x64 processors with either a 32-bit or 64-bit application.

Pervasive.SQL V9.5
Pervasive PSQL v9.5 and higher supports applications running in 32-bit mode on a supported 64-bit operating system and x64 processors.

Pervasive.SQL V9.1 and earlier
Pervasive PSQL v9.1 and prior (including Pervasive.SQL V8) support applications running in a 32-bit mode on the supported 32-bit operating systems and x64 processors.


More information
Visit the Pervasive knowledge base article here


Using Service Accent on a 64 bit CPU
Please read the following article:

Title: Service Accent compatibility with Microsoft Windows
Solution ID: 0404231425525



 
 Related articles

3103, 3012 or 3014 error when trying to access a Pervasive database
Can not link to the WORK table using Pervasive.SQL ODBC
Can't start Pervasive Server Engine, Error 1069, login failure
Configuring Pervasive.SQL ODBC
Connecting to your Service Accent database via ODBC with Pervasive.V8 and later
Error message "1607:Unable to install InstallShield Scripting runtime" when trying to install Pervasive.SQL
Error message "DBU - Access Denied" when entering Pervasive.SQL license key
How to close Pervasive.SQL tables manually
How to configure Pervasive Backup Agent
How to disable the Local MicroKernel Engine under Pervasive.SQL V9

 Additional articles from the white papers

Pervasive Backup Agent v3
Service Accent - Installing Pervasive. SQL
Installing and configuring Pervasive. SQL 2000



For additional resources and information, you can go to the Service Accent Support Centre

Click here to go to the Service Accent Support Centre



Copyright © 2003-2019 Vantage Computing Ltd. All rights reserved. The information contained on this web site is correct as of its publication date.