Michael, I've seen this happen when:
1. The user's PATH statement is messed up and references non-existent drives or folders 2. Your executable has references to unexpected paths that may not be available on the user's system I would ask the user to send you a copy of their path statement, i.e. from the command prompt: set > path.txt I would also review your project to see if it has any unexpected file references. You might also try the following: 1. SYS(2450,1) to force an internal search for resources. 2. SYS(3050 ...) to force a specific type of memory usage (in case your app is being slowed by memory allocation at startup?) Good luck, Malcolm _______________________________________________ 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.
