>Hey all,
>
>I installed SP1 on VFP 8 today. I then thought I could go ahead and deploy the SP1 runtime DLLs to everyone and then at my leisure could re-compile our apps in SP1 and deploy them.
>
>As soon as I put the new VFP8R.DLL and VFP8RENU.DLL out on our server (a stub program then pulls them down and fires up our main app), we started getting help desk calls with the Resource mismatch errors. This means that even though people were still running the old (pre-SP1) application with the newer runtimes (which should be OK, correct?), they were erroring out.
>
>It's not like I was trying to run newer apps with the old runtimes...I can understand why that wouldn't work. But shouldn't old apps run OK using the new runtimes?
>
>If not, it means we are screwed. Our stub program that installs files and fires up the main app is written in VFP. If each SP is not backwards compatible, how can we keep our stub program running with the old runtimes long enough to copy the new runtimes to everybody? As soon as people get the new runtimes, the stub program will cease to function...classic chicken and egg.
>
>I know the ultimate solution would be to write the stub program in something like Dephi so that is would require no runtime at all. But that is not where we are at.
>
>Can someone confirm whether or not old apps should run OK with new runtimes, and if so, why would people have started getting resource errors here?
>
>Thanks,
>JoeK

In my testing VFP8 apps seem to work OK with SP1 runtimes. I have heard reports of errors as you describe when there are copies of both the VFP8 and SP1 runtimes on the same machine, specifically when the SP1 runtimes are in the folder with the exe, and the VFP8 runtimes are somewhere else and registered. Try removing the VFP8 runtime files or unregistering the VFP8 VFP8R.DLL file, or registering the SP1 VFP8R.DLL file.