>>>>Thanks for the info.... I was able to figure out what I had to do. Basically I used a DELETE TRIGGER in the code to shut it down while executing the code.
>>>
>>>And how would you get the darn thing back in again?
>>
>>I only needed it turned off while executing this small program (turned off for speed performance increase - I took care of the referential integrity myself during the deletions). I did not need it turned back on during the execution of the program.
>
>Oh, I see. I thought that DELETE TRIGGER would, indeed, delete it from the database container. Let me speculate: perhaps it doesn't really delete it, if you open the database SHARED?
>
>Hilmar.

Well, the database container is opened exclusively in the code.

After the program finishes, I can change the code to NOT delete the trigger, rebuild the EXE, and run it again on the test data (restored from a backup), and trace it, and the Trigger now executes (I can trace through the stored procedure __RI_DELETE_cont().

So, the Trigger is not permanently deleted... it is shutdown in effect only as long as the database is open (until it is reopened again).

We have any authorities out there on this? Inquiring minds want to know!!

Tommy