Sytze de Boer wrote on 2011-08-11: > Tracey > Thank you for your patience > I've located the issue and my attempt to find a way to (partly) > auto-fix a solution is now working exactly how I want it. > Yes, I agree with others that a Try-Endtry would be much better. > My routine is an ambulance at the bottom of the hill. > If I knew where the problem might occur, I would put systems in place > so it wouldn't occur and I wouldn't need such a routine. > > Thank you again > >
Sytze, You're welcome. I once needed to document a process that had hard coded UNC paths to network shares of tables. This made it hard to see the process in action without changing a lot of code. Then I thought perhaps I could catch it in an error routine, maybe open, modify the select/insert/replace command on the fly and continue. Your scenario sounded similar. How many places does it really happen, could it happen? Not something that can be easily searched with a RegExp. The next step is to make a log when you run into this scenario to allow you to correctly handle the divide by 0 condition before the replace in each place it happens. There is at least one gotcha scenario: If by chance, the error happens in a private datasession, this routine is in the global datasession, you attempt to replace in a table that isn't open, or is open but at a different record?? Tracy Pearson PowerChurch Software _______________________________________________ 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.
