>I already checked the speed without triggers and I have a big performance improvement.
>
>What I want to do is temporarily disable the trigger in my code before I do my processing, do my processing and then re-create the triggers.
>
>Thanks
>
>Eric Dumais

Eric...

I haven't tried this, but the theory is sound... use

cUTrig = DBGETPROP('MyTable','TABLE','UpdateTrigger')
cDTrig = DBGETPROP('MyTable','TABLE','DeleteTrigger')
cITrig = DBGETPROP('MyTable','TABLE','InsertTrigger')

Then you can

REMOVE TABLE

Then

ADD TABLE
CREATE TRIGGER

But... also keep in mind when you remove a table all info stored in the DBC about the fields and indexes is also removed... stuff like defaults, rules, primary index, etc... you will have to store all these things too. Probably the best way to do it is to open the .DBC as a table, and find the record for the table and modify the values of the field.

I believe SDT gives you functions to do this kind of manipulation.

BOb