Do you use the try-catch construct in your error routine? The thing is that with atomized try-catches throughout the code, you can pinpoint the error more accurately, whereas without it, VFP will show an error which is apparently not connected to the culprit routine or will point in the wrong direction, driving you nuts when you try to figure out what the heck happened.
BTDT Rafael Copquin El 17/04/2012 01:31 a.m., Sytze de Boer escribió: > My system has an error routine which has been in place for years > > A client rang me with a problem and for the life of me, I could not > understand the error message > The error pointed me to the program module, and line number where the error > was occurring > > It was crapping out on > Use winkdata > Locate For Alltrim(ktable)='WINDCONS' > > The error message was Variable ktable not found > ktable is a field in the table > > The problem only occurred if a 2nd person logged into the system > After 3 hours we determined the problem was a corrupt config.fpw file and > the system > was not opening tables in shared mode. > > Questions I have > Why variable not found when it should have Access denied (or somesuch) > My config.fpw always has the line exclusive=off > Is that the best place to have it. > Does the fpw file supersede the line set exclusive on/off somewhere in the > app > _______________________________________________ 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.
