Michael, Like other posters I believe your app is hitting a path/file that doesn't exist on the problem pc. Perhaps a file reference *buried* in your project to a removable drive or network path not present/active on your problem pc.
Ideas: 1. Go to your command prompt, simplify your PATH= to just windows related folders, then run your app. 2. If VFP 8+, try changing the default value for sys(2450) so that it looks for all file references internally. If the above ideas don't help, monitor your app via SysInternal's utility to see what file's its trying to reference. Info following my signature. (BTW: I would try this anyway to make sure you can eliminate the bad path/file references that techniques 1 and 2 will mask) Good luck and let us know if any of these ideas help, Malcolm <quote> Process Explorer for Windows v10.21 http://www.microsoft.com/technet/sysinternals/utilities/processexplorer.mspx NOTE: "a system monitoring tool that not only replaces Regmon and Filemon by including file system and registry monitoring, but adds process, thread, and DLL monitoring as well as advanced filtering, event information, and basic data mining capabilities." Ever wondered which program has a particular file or directory open? Now you can find out. Process Explorer shows you information about which handles and DLLs processes have opened or loaded. The Process Explorer display consists of two sub-windows. The top window always shows a list of the currently active processes, including the names of their owning accounts, whereas the information displayed in the bottom window depends on the mode that Process Explorer is in: if it is in handle mode you'll see the handles that the process selected in the top window has opened; if Process Explorer is in DLL mode you'll see the DLLs and memory-mapped files that the process has loaded. Process Explorer also has a powerful search capability that will quickly show you which processes have particular handles opened or DLLs loaded. The unique capabilities of Process Explorer make it useful for tracking down DLL-version problems or handle leaks, and provide insight into the way Windows and applications work. Process Explorer works on Windows 9x/Me, Windows NT 4.0, Windows 2000, Windows XP, Server 2003, and 64-bit versions of Windows for x64 processors, and Windows Vista. </quote> _______________________________________________ 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.
