The current VFP8 replaced an older version.

And yeah, I get that the runtime engine will open the resource file first thing, but it should either close it (at best) or ignore it (at least) once you set it off. I've never had an application 'magically' have the resource turned back on after the app has been running for a while.


>It is especially a problem if you have a mixture of different versions of VFP and FPW programs -- newer runtime tends to automagically "upgrade" the resource file and make older runtimes think it is corrupt. If I'm not mistaken, unless you have RESOURCE=OFF in the config.fpw, the runtime engine opens the resource file *before* the main PRG is started.
>
>>First line may already be too late, at least to avoid problems. Instead you need RESOURCE=OFF in your config.fpw file, which should be included in the exe. However, in your case it sounds like you have SET Resource On somewhere in your code.
>>
>>>Hey all
>>>
>>>Got this application running on about 160 machines and all of a sudden we're getting "Resource file corrupted - overlay with new?" error in the middle of running. First command in my main program is "Set Resource OFF"
>>>
>>>Now, I can almost understand getting it when the app first fires off, but not during the running.
>>>
>>>What's going on?