AKAIK there's no elegent way to prevent the trigger from firing, precisely because other users can access it at the same time. The brute force approach would be to drop the trigger, perform the update, then recreate the trigger. You'd have to lock the table to prevent other users from attempting updates at the same time.
This is a pretty drastic approach, as you can imagine, and best saved for after-hours processing if possible.
Dan LeClair
www.cyberwombat.comSET RANT ON - The Wombat BlogLife isn’t a morality contest and purity makes a poor shield. - J. Peter MulhernDisclaimer: The comments made here are only my OPINIONS on various aspects of VFP, SQL Server, VS.NET, systems development, or life in general, and my OPINIONS should not be construed to be the authoritative word on any subject. No warranties or degrees of veracity are expressed or implied. Void where prohibited. Side effects may included dizziness, spontaneous combustion, or unexplainable cravings for dark beer. Wash with like colors only, serve immediately for best flavor.
