Kbase 17821: .p trigger code via OIB fails with (2882)
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
.p trigger code via OIB fails with (2882)
If a remote ESQL or ODBC client is trying to fire a .p schema trigger
via the Open Interface Driver (OIB/OID), it will receive the
following error:
Cannot compile <name>. This module requires precompiled database
schema trigger procedures (and sub-procedures). (2882)
PROGRESS tried to execute a 4GL procedure that has not been
precompiled, and the PROGRESS 'prooibrk' executable does not have the
4GL Compiler. For example, ESQL clients cannot compile 4GL code,
but can cause database schema trigger procedures to run when
executing SQL statements. For this reason, the trigger code defined
in the database schema needs to be compiled and referenced as a .r.
The .r file must reside on the system where the database broker is
installed and relies on the PROPATH environment variable.
You may also include the -trig parameter on startup of the OIB
broker to force the trigger to run from a particular directory or
library. Please refer to the V8 Systems Reference Guide for more
information on the -trig parameter.
WINDOWS/NT GUI:
From the Data Dictionary, choose EDIT PROPERTIES and select the
TRIGGERS button. Edit the Procedure: fill-in field to include the
.r trigger code.
UNIX CHUI:
From the Data Dictionary, choose MODIFY TABLE from the SCHEMA menu,
enter the tablename, and select TABLE TRIGGERS. Include the .r
trigger code in the appropriate fields.
For more information on defining Schema Triggers, please refer to:
V8 SQL Guide and Reference
V8 Programming Handbook,
4/2/98
Progress Software Technical Support Note # 17821