Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
post-query trigger question 3
- Thread starter rabrabbie
- Start date
-
1
- #2
-
1
- #3
A POST-QUERY trigger actually fires after the posting but still depends. For instance you could be having a field for DEPT_ID and another one for DEPT_NAME.
You can use a POST-QUERY trigger on the DEPT_ID field such that when you input the DEPT_ID then the DEPT_NAME appears.
You can use a POST-QUERY trigger on the DEPT_ID field such that when you input the DEPT_ID then the DEPT_NAME appears.
-
1
- #4
...except that you can't put a POST-QUERY trigger on an item, only on blocks (and forms).
It fires once for every record, just after it is first retrieved from the database and just before the fields on the screen are populated. You can use it to populate lookup fields as Kido says, though it's more efficient to do this sort of thing with a view.
A sometimes useful feature of POST-QUERY triggers is that if you raise FORM_TRIGGER_FAILURE in the trigger, that record will not be displayed to the user. This can come in handy when implementing row-level security procedures.
-- Chris Hunt
It fires once for every record, just after it is first retrieved from the database and just before the fields on the screen are populated. You can use it to populate lookup fields as Kido says, though it's more efficient to do this sort of thing with a view.
A sometimes useful feature of POST-QUERY triggers is that if you raise FORM_TRIGGER_FAILURE in the trigger, that record will not be displayed to the user. This can come in handy when implementing row-level security procedures.
-- Chris Hunt
- Status
Similar threads
