Can someone tell me what all the FORM_TRIGGER_FAILURE does in a
POST-QUERY trigger when raised? Looking at help tells me that is
flushes the current record.
I have a form that is extremely complex. It has a pre-query trigger
that sets the default where clause based on what a user wants to query
on. At this point there is a possibility of 5 different complex where
clauses. There are (were) 2 other selection criteria that were not
set up in the pre-query that the post-query trigger is doing a
FORM_TRIGGER_FAILURE to drop the record that doesn't match. I say
"were" because one of them I was able to eliminate, but the other
would be impossible to eliminate. Let me say that ALL of the code
works exactly as it was designed. Great!....except it is slooooooow.
The problem has been narrowed down to the raise form_trigger_failure.
Execute all the code exactly except comment out the raise
form_trigger_failure, the query returns immediately....more records
than needed of course.
Also this problem actually started when this unchanged form was
converted from 4.5 to 6.
Any info would be appreciated!
