I'm afraid posting the project wouldn't be possible. Even if I got the OK from my boss to post the code, it takes a few hours to get it all configured to run properly in Visual Studio. Obviously that's a bit much to ask from anybody, so I understand if you can't help at all. I was really just hoping for a miracle I guess. :/

As for the paths, no, I don't use any absolute paths in the program or anything like that. All paths are either relative (our files) or gotten from Windows (such as temporary files folder).

I do have one question that might be related. In version 5 of our software, we distributed our EXE with mfc80.dll and the manifest files (along with the others). But in version 6 we moved from InstallShield to a VS Deployment Project which doesn't include any of those files. I'm assuming that it uses a shared DLL in the Windows folder. Could this possibly be a source of error? Could different versions of MFC be causing this issue? I read a page yesterday (http://go4answers.webhost4life.com/E...id-210535.aspx) saying that VC6 didn't have a problem with some parameters but VS2010 did. Is there a way to include the necessary DLLs in the installer as to avoid version issues?