Designer/2K Table API's and Triggers
From: Louis Cohen <louiscoh_at_sprynet.com>
Date: Sun, 2 Aug 1998 12:11:17 -0700
Message-ID: <6q2ddv$8nh$1_at_lal.interserv.com>
Has anyone used the Designer/2K v2.1 table API's and triggers yet? How about INSTEAD OF triggers on views (where the view is the base table table for a form block and the INSTEAD OF triggers handle inserts/updates/deletes?
Date: Sun, 2 Aug 1998 12:11:17 -0700
Message-ID: <6q2ddv$8nh$1_at_lal.interserv.com>
Has anyone used the Designer/2K v2.1 table API's and triggers yet? How about INSTEAD OF triggers on views (where the view is the base table table for a form block and the INSTEAD OF triggers handle inserts/updates/deletes?
We are starting to design a new application with them and were wondering what people thought about them.
Does anyone know how the error handing in the table API's (using CG$ERROR) interacts with error handling code in generated forms using CG$FORM_ERROR? That is, what happens in the form if an insert/update/delete causes the table API to raise an exception? Received on Sun Aug 02 1998 - 21:11:17 CEST