Kbase P6708: Error 425 and 725 when compiling the application using the S
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/16/2003 |
|
Status: Unverified
SYMPTOM(s):
Error 425 and 725 when compiling the application using the Schema holder
Table <table> is in database <db name> and <db name> (425)
Unknown or ambiguous table <table>. (725)
Schema holder contains multiple logical names
The schema holder was created from the separate but identical multiple foreign databases
CAUSE:
This is a normal behavior. If there are multiple but the identical databases connected, the query needs to have the logical name specified before the table name with a dot (example: sports.customer) else the compiler would be in confusion as to which database the table should be picked from. When an application needs to be compiled, the foreign database need not be connected. The schema holder retains the foreign tables and fields information in the hidden tables for the mapping purposes. For instance, if the progress database contains a field name with dash like cust-id, the foreign table will not support this naming convention. Instead the foreign database will convert the dash to underscore that is as cust_id. In order to retain progress functionality, progress keeps its own naming convention and keep the mapping of the field from cust-id to cust_id in the schema holder.
FIX:
There are 2 choices to solve this problem:
1. Specify the logical name before specifying the table name separated by a dot or period. Example: sports.customer.
OR
2. Create a separate schema holder for each of the foreign database.