OK - will try this suggestion next - after trying Dave's... -K-
-----Original Message----- From: ProfoxTech [mailto:[email protected]] On Behalf Of Richard Kaye Sent: Thursday, September 27, 2012 10:25 AM To: [email protected] Subject: RE: A Debugging Problem... Another option would be to wrap the offending code block in a TRY..CATCH. Then you shouldn't have to know your known unknown (i.e. which index is missing) ahead of time. Just stick a messagebox in the catch block with the pertinent details. -- rk -----Original Message----- From: ProfoxTech [mailto:[email protected]] On Behalf Of Dave Crozier Sent: Thursday, September 27, 2012 10:18 AM To: [email protected] Subject: RE: A Debugging Problem... Kurt, if the app errors out and allows you to go into step mode then you can look at the stack to see how you got to the error point. if there is already error handling that is may be screwing things up then override with "on error set step on" will dump you into step mode at the error point. Dave [excessive quoting removed by server] _______________________________________________ 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/289ea162f5642645b5cf64d624c66a140e260...@us-ny-mail-002.waitex.net ** 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.
