Q: Forms and non-database fields
From: Eugeny Jarkov <ezharkov_at_dxcern.cern.ch>
Date: Sun, 25 Apr 1993 17:03:13 GMT
Message-ID: <1993Apr25.170313.27180_at_dxcern.cern.ch>
Date: Sun, 25 Apr 1993 17:03:13 GMT
Message-ID: <1993Apr25.170313.27180_at_dxcern.cern.ch>
I am using "SQL*FORMS_VERSION = 03.00.16.04.02".
table T1 (ID number, F1, ...);
table T2 (ID number, NAME char(10));
block B1 with the base table T1 (so "NAME" is non-database field).
ID NAME F1 ...... ____ __________ _____ ......
I allow input into "ID" and "NAME". For "NAME" field I use "ON-VALIDATE-FIELD" trigger:
select ID from T2 where NAME=:B1.NAME
I also use "POST-QUERY" trigger:
select NAME from T2 where ID=:B1.ID
The problem:
NAME is selected in the POST-QUERY trigger, ON-VALIDATE-FIELD fires, ID is selected in the ON-VALIDATE-FIELD, block B1 is marked as CHANGED. The questions: Is it possible to prevent ON-VALIDATE-FIELD from firing? Is it possible to setup that "No changes to commit"? Is there another technique to do this?
Thanks! Received on Sun Apr 25 1993 - 19:03:13 CEST