Coincidentally I am typing this on a customer's site who had exactly this error with Terminal Services users. Server is Win 2k SP4. The app is VFP6, all I did to change things was put the server into install mode for Terminal Services, ran the Installshield installer to upgrade, then put the server back into execute mode. Which has worked a billion times before. After the last one however the TS users get the 0xC0000007 error, normal network users are fine. Also I got the error running the app while sitting at the server.
By default the shortcut to it runs the exe via O:\name.exe, where O: is \\servername\appfolder, which in turn is a share of d:\appfolder on the actual server. I changed the shortcut to run as d:\appfolder\name.exe instead of via the mapped drive, and I don't get the error anymore. Hope that helps. -- Alan Bourke [EMAIL PROTECTED] -- http://www.fastmail.fm - And now for something completely differentÂ… _______________________________________________ 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.
