How to set the PUB qualifier in the Windows registry to avoid prefixing it in existing reports?

por | 21 febrero, 2018

Environment Product: Progress
Version: 9.1x
Product: OpenEdge
Version: 10.x
OS: Windows
Other: Crystal Reports
Question/Problem Description
How to avoid setting the pub qualifier before each table name in a Crystal Report ?
How to set the pub qualifier in Windows registry?
How to use existing SQL-89 Crystal Reports with SQL-92 ?
How to set the default schema in the registry?
How to use existing SQL-89 code with SQL-92?
Steps to Reproduce
Clarifying Information
Error Message
Defect/Enhancement Number
Cause
Resolution

All 4GL tables, by default, are owned by PUB. When using SQL-92, all queries must specify the table owner. This was not the case when using SQL-89.

Add the «DefaultSchema» string value set to «PUB» in the registry:

HKEY_CURRENT_USER\Software\ODBC\ODBC.INI\<your DSN name>

– OR –

HKEY_LOCAL_MACHINE\Software\ODBC\ODBC.INI\<your DSN name>

This entry allows you to keep your existing code written with the ODBC SQL-89 Driver. Reconnect to the database with the client and test the application again.
Workaround
Notes
Attachment
Fecha de la última modificación 13/09/2015 4:49
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an «AS IS» basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.
Disclaimer

The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an «AS IS» basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.

Feedback

Was this article helpful?

Copyright © 2017 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.

Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.
Terms of Use Privacy Policy Trademarks License Agreements Careers Offices