Previous question: SQL Server Linked Server to MS Access - DSN Architecture Mismatch Error However, there does not seem to be one for Pervasive v10 at all, only for PSQL v11+, which does not help me in this case. I had a similar issue not long ago trying to connect to a Microsoft Access database, but with help here I was able to obtain the 64-bit ODBC driver for Access. The specified DSN contains an architecture mismatch between the Driver and Application With its emphasis on reuse and adaptability, DataConnect is engineered to help you cost-effectively. Actian DataConnect is a hybrid integration solution that enables you to quickly and easily design, deploy, and manage integrations on premise, in the cloud, or in hybrid environments with no limits on data types or volumes. Disclaimer This page is not a piece of advice to remove Pervasive PSQL v10.10 Workgroup (32-bit) by Pervasive Software from your computer, nor are we saying that Pervasive PSQL v10.10 Workgroup (32-bit) by Pervasive Software is not a good application for your PC. With the release of Pervasive.SQL 7, Pervasive Software started including the SQL engine 'in the box' with the Btrieve engine. This file is normally located in C: BTI WINNT BIN.

The core engine module is called NTMKDE.DLL and is a good place to start. Version by checking the dates and embedded version information from various files. Version 11 will help your application take advantage of multi-core hardware. Pervasive SQL (PSQL) is a database management system. I am setting up a Linked Server in SQL Server via ODBC connection, but I am receiving this error that has given me a lot of pain in the past: I am using the 64-bit version of SQL Server 2016 Express, trying to connect to a 32-bit Pervasive SQL v10 database.

Pervasive psql v11 free download