We have successfully used this approach several times to find out what program was causing the problem. We used the call stack and also some info in our named commons to write to a debug file that we created for this process. We used to use dummy indexes to debug this type of problem. But triggers work just as well. -Rod
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Bessel, Karen Sent: Thursday, October 22, 2009 10:23 AM To: U2 Users List Subject: [U2] Trigger Question My application is creating some bogus records in a file, somewhere...we are unable to pinpoint when & where & what the user is doing to create these records, but they're popping up every couple of weeks. I'd like to create a trigger to tell me when these records appear so that someone gets notified, instead of inadvertently falling across the data days later. Since I don't know where this bogus data is being created, is it possible for the trigger subroutine to tell me what the call stack/writing program is. Thanks, Karen Karen Bessel Software Developer Tyler Technologies, Inc. 6500 International Parkway, Suite 2000 Plano, TX 75093 Phone: 972.713.3770 ext:6227 Fax: 972.713.3780 Email: [email protected] Web: http://www.tylertech.com _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
