Kbase 15436: schema triggers and s/e Unable to save trigger code in file
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
schema triggers and s/e Unable to save trigger code in file
If you receive the error "Unable to save trigger code in file" while
checking syntax or saving a Table Trigger in the Data Dictionary
utility, check the following possible causes:
1> The file may be set up READ-ONLY. To find out, run the Triggers
report from Database -> Reports. This will show the full file
specification for all triggers associated with the database. If a
relative path was specified when the trigger was initially created
using the Table Triggers application, the DLC variable will be
translated into the full file spec. For example, with the sports
database, the trigger for CREATE of Customer table is shown as
sports/crcust.p. In the Triggers Report, it would appear as
usr1/dlc/sports/crcust.p if DLC were defined as /usr1/dlc.
Once you have the full file spec, use ls -l (UNIX platforms) to see
the protection on the file.
2> The directory or subdirectory specified in the Table Triggers
application must exist *before* you attempt to save the trigger code.
Progress Software Technical Support Note # 15436