What is it you're trying to accomplish? Simply preventing all deletions? If that's the case, since deleting is not forever in VFP, why does it matter that the delete trigger fires after the record is deleted. Couldn't you just recall the record in the trigger?
MB Software Solutions wrote: > I rarely use the DBC events and triggers too (although I must say that I > love the dbc_BeforeOpenTable(cTableName) event to block unwanted > visitors!), but I thought the DELETE TRIGGER code fires AFTER the record > is deleted? It'd be great if it were like Oracle in this instance where > you've got On_Delete_Before and On_Delete_After events. (I know they're > not named that in Oracle, but you get the idea.) > > -- 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: ProFox@leafe.com 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.
