>Hello Whatever < gd&r >,
>
>Well, if the situation is as critical as it sounds (he commented about it another thread), I wouldn't think twice about it. If I didn't have another machine available that didn't have VFP7, I would be doing a clean Windows install lickity split on a machine. Install VFP6 only, recompile the app (hopefully they have current backups, in case something in the project has gone awry), and get that baby redistributed.
>
>-Steve

Steve;

That would be my plan of action also. Hope they used VSS or a similar tool. If this solved the problem I would not try using VFP 6 and 7 on the same machine again.

Instruct users - revert to previous version of exe or "PUNT"! :)

Tom



>
>>Steve;
>>
>>Call me paranoid or whatever. I keep one version of VFP (etc.) on one machine. So I do not trust what some people say about keeping multiple versions of software on the same computer. With the name Thomas, I am allowed to doubt! :)
>>
>>Sometimes it helps to revert back to the vanilla Windows Drivers, to resolve these types of problems. The question is (there are really many) what drivers are installed on the users machines? Sounds like something is really wrong here.
>>
>>Another thing I do is test on clean machines – reformat the HD, install the OS and go from there.
>>
>>Hope Larry finds the answer to this problem.
>>
>>Tom
>>
>>