Hi Richard, >> one would be to capture the current system state at that point in time >> including call stack, program/method, etc and log it for me and two would be to return false on the trigger and automatically recall/revert the deletion.<<
We had the same problem in the last month with a new application written by someone else, which we are taking over support. The customer called complaining the data was automagically deleting itself. We have not even cracked open the source code yet. Argh. We did something like you are suggesting in the delete triggers so we could implement something fast without rebuilding the EXE. We added audit tables to the application and made sure every deletion copied the record to the audit table along with the call stack, GETFLDSTATE(-1), SYS(0) for the machine and user, and date/time of the event so we could learn how the records were disappearing. It worked like a charm after we corrected something we did not expect, the developer has a SET EXCL ON somewhere in the code and it was randomly opening up our audit tables exclusively which wacked the trigger code when a second user tried to open up the audit table. Fun times. Fortunately, the customer was understanding. Rick White Light Computing, Inc. www.whitelightcomputing.com www.swfox.net www.rickschummer.com _______________________________________________ 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.
