>>>Disclaimer - I have had several problems in the past with resource files and I do not fully understand them.
>>>
>>>I run vfp5.0. These two problems seemed to start when i installed vfp6.0. I run both 5 and 6 on my machine.
>>>
>>>1) I can execute my exe (built from 5.0) from within vfp5.0 (program, do, from the menu). But, if i double click on the exe from explorer I get the dreaded "resource file version mismatch". I do not even need the resource file in this small exe and included a config.fpw that has "resource=off". Nowhere in the exe is the resource file set. Several of my 5.0 exe run ok, but many get the resource version mismatch. I renamed my VFP6.0 foxuser.dbf hoping that might help, it did not.
>>>
>>>2)another problem is when i double click on the pjt or pjx from explorer. I have VFP 5.0 set up to open those file types. Vfp5 does open, but then i get "unrecognized command verb" and the project comes up in a prg type window (not project manager) with the unprintable characters. Project opens ok if I open it from within VFP5.0, but I am in the habit of opening from explorer, and now that does not work.
>>>
>>>What is up will this craziness?
>
>>I suspect that it is not the FOXUSER file that's a problem, but the VFP Runtime registry values; IOW, your app is compiled under VFP 5, but because of how VFP 6 was installed, VFP 5 .EXEs are invoking the VFP 6 runtime environment. To prove this out, make a copy of the project, compile it under VFP 6 making no ther changes, and then run the VFP 6 executable. If it works (and it probably will) then the registry entries for VFP 5 got frobbed by your VFP 6 install. If you want to reset your registry associations to the defaults for VFP 5, run VFP 5's development .EXE with the /R parameter from the Start Menu/Run box or a command line; this will restore the default registry mappings. To switch back to VFP 6, you can do the same thing woith the VFP 6 development .EXE. if you do this a lot, build a couple of shortcuts to save yourself typing time.
>
>I tried entering "c:\rt50c\convqmrpt /R" from the Start Menu/Run box, and there was no difference in my ability to get by the "resource version mismatch" or double clicking the project frm explorer.

Not the compiled executable, the VFP executable itself. If your VFP5 development executable (the one pointed to in the shortcut to VFP 5 in the Start Menu) is C:\VFP5\VFP.EXE, enter the following in the Run box:

C:\VFP5\VFP.EXE -R

Take a look at the Startup Options/Command Line Switches topic in the VFP 5 help file for more details. It actually calls for -R rather than /R in the docs.
>
>Any other ideas?
>
>Brenda