We have some triggers placed on certain Baan tables. We recently had users complain that a report (with data generated by two specific triggers) was not working properly. Upon investigation we found that these two triggers were gone. We recreated the triggers, but we are curious as to how they were removed. They were not deleted directly (by a DBA or sql script). Would modifying the table definitions in Baan (i.e. adding a field) for the table that also has a trigger cause the trigger to be removed?

Any other ideas/suggestions?

Thank you.

Yes, in older versions of baan and in some cases with newer versions of baan, when you make a table change it drops and re-creates the table which wipes out your triggers.

Which is one reason, why it's always considered bad-form to use triggers on baan tables.

Dave

Thank you for your response. I agree, however business rules require them.

It's quite easy to create a script which grants access rights back for example every night...that's how we do.
We have also trigger monitoring scripts to see if they are gone.

i don't like triggers because of the error messages they tend to generate.

For example, you create a trigger on your item master to update a record another table. Then that other table changes in a way that breaks your trigger.

You'll be alerted to the problem because someone is getting an error 512 (or something) on the item master table. If you're lucky you'll remember, "oh, i have a trigger and that's probably failing" but most likely you'll spend 2 days looking into why "Baan broke my item master".

Even worse is when you leave the company and a new admin or dba comes in. they might spend weeks looking for the problem.

Dave

^Only somewhat legit reason I can think of for triggers on Baan tables is to update data in non-Baan tables for something like a data warehouse. Even then, you have all of the issues with reconfigs, etc...