Kbase P53610: _File record not on file (138) during execution of schema tr
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
14/11/2003 |
|
Status: Unverified
FACT(s) (Environment):
Progress 8.3x
SYMPTOM(s):
_File record not on file (138) during execution of schema trigger
** <file-name> record not on file. (138)
Multiple databases connected.
Database trigger reads _File metaschema table to retrieve field names (for auditing purposes)
CAUSE:
The _File metaschema table contains only information of the database that table appears in.
In this case, the error 138 is most likely caused by trying to look up a table that is located in a different database than the _File table scanned, and there will be no record for this table.
FIX:
Make sure the _File table of the correct database is referenced by qualifying with the database name.
The database name can be retrieved by using the LDBNAME(BUFFER ...) function on the buffer of the table that is being looked up.