That's a bird of a different feather... <g> How about wrapping that TABLEUPDATE in a transaction, too?
MB Software Solutions wrote: > I had a situation where some sort of snafu/bug was causing records to be > deleted during a TABLEUPDATE gone awry. As of 3:30am this morning, I've > now fixed the bug (I think!) but this question was posted as a "safety > valve" way to absolutely ensure that even if the TABLEUPDATE() fowled > up, the records didn't get deleted -- Richard Kaye Vice President Artfact/RFC Systems Voice: 617.219.1038 Fax: 617.219.1001 For the fastest response time, please send your support queries to: Technical Support - [EMAIL PROTECTED] Australian Support - [EMAIL PROTECTED] Internet Support - [EMAIL PROTECTED] All Other Requests - [EMAIL PROTECTED] --------------------------------------------------------- This message has been checked for viruses before sending. --------------------------------------------------------- _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
