Dont know which version of VFP your dealing with, but its the VFP exe/dlls that are out of synch...

As we all know, typically the VFP files are installed somewhere respectively down the Program Files directory and sticks a few files in the Windows\System32 directory. There appears to be a cross-over of dlls.

To get through, you may want to copy the respective dlls in the EXE root directory where launched... then you can trace back to see which ones may be out of synch from the other directories (Program Files\VisualFoxPro and Windows\System32).

This happened for another person I helped and thats what we found. All was fine after that. It had nothing to do with the FoxUser files.




>Greetings all.
>
>Our application is deployed via an InstallShield setup that I developed using IS11. The VFP portion of the client installation is handled through VFP's own merge modules that are added to the IS project. Up till now, all of our clients running 2000 and XP are able to successfully install and launch our application.
>
>We have one client (it's always just one, isn't it?) running XP Pro SP2 who has tried to install the runtimes and launch the application. When doing so, he gets the following messages:
>
>Visual Foxpro cannot start. Could not load resources.
>Resource file version mismatch.
>
>I told the client to delete FOXUSER.* from the executable directory. There are no other instances of those files anywhere on the workstation. We've scheduled a Webex session tomorrow so I could look at things, including the registry just to make sure that the runtime classes got registered correctly.
>
>Any other ideas as to what I should look for?
>
>Laterness,
>Jon