>I'm writing an application where I will be updating my database from an XML message. The tables I am updating have insert and append triggers on them. I don't want to fire these triggers if my particular application is the one updating the tables.
>
>I don't have exclusive database access, so I can't exactly change the trigger to suit my needs.
>
>Any thoughts? Is there a simple command I can run that disables the triggers until I issue another command?

That's the thing with triggers, they always fire, no matter how you access the database (VFP IDE, application, ODBC).

Can you modify the trigger to check an application property that your application sets? If it exists, the trigger could immediately return without doing anything.