It is USUALLY the file BEFORE the error, at least in my experience. Another thing I use to debug hard stuff OR to document a system is add a single line to each routine, something like "iff(vjb_document, wait window + prog(), "")
That way I can turn on vjb_document and watch the wait windows and drill down to exactly which routine is causing the problem. Virgil Bierschwale Armstrong and Skipper Real Estate (830) 329-6774 Cell (830) 864-4726 Home (830) 864-4799 Fax http://www.geocities.com/vbierschwale/ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Crooks Sent: Tuesday, September 19, 2006 8:39 AM To: ProFox Email List Subject: RE: VFP7: Terminal server errors out On Monday, September 18, 2006 4:41 PM Jeff Johnson wrote: >David: I have been running apps successfully on Terminal Services. It took a bit of work to set it >up, mainly because of the way TS maps drives. The tricky part for me was establishing unique >temporary files for each user. Yes, if the user starts the application correctly then each user has their own directory for temp files. >Can you tell which file can't be read? What code is generating the error? No, one of my biggest pet peeves of the VFP error handler. If I get an error of file not found could it at least tell me the name of the file? Thanks! David L. Crooks [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 ** 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.
