Hi Fred,

>>If you are the author of the trigger, you can consider having the trigger give feedback on the reason for failure. I use a public variable to store a message string explaning the reason for failure. (I know public variables have dangers, I just haven't come up with a better solution, yet) This also slows down updates to my database from outside my application. They have to declare the public variables or the triggers always fail!
>>HTH,
>
>If you MUST < g > use a public variable, do a TYPE() or a VARTYPE() on them to see if they exist, and if they don't, then do a PUBLIC yourvariable inside your trigger.

Sorry if I wasn't clear... I have found it a GOOD thing to not test TYPE() in the trigger. This stops some updates outside of my app. Not too hard to figure out, but it stopped at least one Access user! <VBG>