Hello progress-talker,
I developed several application within adm 1 - and there I used the database-triggers. The usual delete-triggers for keeping consitency produces a message "...can not be deleted - because records available...".
So within adm2 there is an other structure - making the "business-logic" within the sdo`s and the frontend without any database-access.
So what is the "perfect" place for the delete-trigger - within a database-trigger, or within the client-frontend?
Thankyou in advance
andi
I developed several application within adm 1 - and there I used the database-triggers. The usual delete-triggers for keeping consitency produces a message "...can not be deleted - because records available...".
So within adm2 there is an other structure - making the "business-logic" within the sdo`s and the frontend without any database-access.
So what is the "perfect" place for the delete-trigger - within a database-trigger, or within the client-frontend?
Thankyou in advance
andi