Re: Forms

Patrick,

I am guessing that your detail blocks are not base-table blocks. Check the base_table property in each detail block. If the property is null, then you have triggers in the blocks that issue explicit DML statements rather than the implicit one performed by FORMS when a base table is updated.

FORMS is not aware of the issuance of DML statements and assumes that there is nothing to commit when the user enters [Commit].

To suppress the error message, you need to define an ON-ERROR trigger. Check for the error number using the ERROR_CODE function. To ignore the error, issue the "NULL; " builtin. You'll need to sample ERROR_CODE, ERROR_TEXT, and ERROR_TYPE at the beginning of the trigger and then use the local variables internally. The information sampled by these functions is transient, i.e. once sampled they disappear. Use the MESSAGE builtin to display your sampled values for those messages you want the user to see.

If this doesn't work, try the ON-MESSAGE trigger with its corresponding builtins: MESSAGE_CODE, MESSAGE_TYPE, MESSAGE_TEXT. One of these 2 triggers should fire whenever FORMS finds something to complain/inform the user about.

Al Received on Wed Jan 22 1997 - 00:00:00 CET