Can not link to the WORK table using Pervasive.SQL ODBC

Article ID: 0306241022457 - Last Review: 22 May 2006 by jasonl - Revision: 1 - Views: 5282

Trying to link to the WORK table using the Pervasive.SQL ODBC interface in Pervasive.SQL 2000i results in an error. Linking to other tables works correctly and data can be viewed

Investigation by Pervasive has revealed that the table name WORK is a reserved word in the Pervasive.SQL ODBC driver and causes it to fail.

If possibile, enclose the table name WORK in double quotes, for example:

Some applications, such as Microsoft Access do this automatically and are able to retrieve the data in this table correctly. However, some applications like Crystal Report do not enclose the table name in quotes, causing the Pervasive.SQL ODBC driver to fail.

There is no workaround available if you are unable to specify the format of the connection string manually.

 Related articles

Configuring Pervasive.SQL ODBC
Unable to configure Pervasive.SQL ODBC via Remote Desktop
3103, 3012 or 3014 error when trying to access a Pervasive database
Can't start Pervasive Server Engine, Error 1069, login failure
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
Installing Pervasive.SQL results in an 'Installation was interrupted' message

 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-2023 Vantage Computing Ltd. All rights reserved. The information contained on this web site is correct as of its publication date.