Is there any way to specify default database for ambiguous tables? - Progress Community

Loading

Skip to Main Content

Is there any way to specify default database for ambiguous tables?

When code was written assuming a single connected database but now has multiple databases connected where there are now duplicate table names between the connected databases is there an easy fix to the ambiguous table name compile error?

Feb 8, 2012
Knowledge

Title

Is there any way to specify default database for ambiguous tables?

URL Name

000028322

Article Number

000150760

Environment

Product: OpenEdge Version: 10.x, 11.x OS: All supported platforms

Question/Problem Description

How to specify a default database for ambiguous tables?

How to fix the ambiguous table name compile errors 725 425?

In the following Use Cases, is there a way to tell the session that when encountering an ambiguous table name it should assume a specific default database name?

Application code was written assuming a single connected database but now has multiple databases connected where there are now duplicate table names between the connected databases.
Application was written under the assumption that only one database was going to be connected and consequently none of the application code prefixes table name references with the database name. Unfortunately now the application has multiple databases connected and there are now duplicate table names among the connected databases and this causes the ambiguous table name compilation error.

Steps to Reproduce

Clarifying Information

Error Message

Table <table> is in database <db name> and <db name> (425) Unknown or ambiguous table <table>. (725)

Defect Number

Enhancement Number

Cause

Resolution

There is no way to specify a default database name to use to resolve ambiguous table name references.

The source code will have to be modified to include the required database name prefix to the table names.

For example, setting up an include file with all database references in it and then defining a buffer works well in the above use cases:

DEFINE BUFFER buffer-name FOR {&db-table-buffer}.

Upgrade to OpenEdge 11.7.0 and use the Compiler the "require-field-qualifiers" option.

No ambiguous buffer error with unqualified field reference

Workaround

Notes

Keyword Phrase

Last Modified Date

11/20/2020 7:39 AM

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.

Loading

Is there any way to specify default database for ambiguous tables? - Progress Community