>>>A VFP APP uses runtimes version of calling application. A VFP EXE always runs with runtimes it was built with. Check Re: RUN command botching up SET PATH commands... Message #1169622 for one of the ways to run VFP exe from inside other VFP program.
>>
>>
>>Tested:
>>
>>VFP9 Executable calling a VFP 7 executable will use the VFP 9 DLLS.
>>
>>

>>VFP 9 exe -- VFP 7 exe
>>VFP 9 dll -- VFP 9 dll
>>

>>
>>But I think this is what you meant. I don't know about apps, but this is the way it works with our production Executable. We had to compile the VFP 7 executable into a VFP 9 executable to make the UI look correct.
>
>Sorry, my answer wasn't complete. VFP APP always uses runtimes version of calling application. However, a VFP EXE can be called 2 ways, with DO command or using RUN/SHELLEXECUTE()/etc. In the first case it's the same as calling VFP APP, it uses runtimes version of calling application. In the second case the VFP EXE runs as independent application with it's own runtime.

>Calling Program   DO MyVP7.EXE   RUN MyVP7.EXE
>MyVFP9.EXE
>VFP9*.DLLs        VFP9*.DLLs     VFP7*.DLLs
>

Thank you. I tested this in my environment. We use a launch program to instantiate a few VFP applications. When the exe is used with the "DO" command it is created in the same working space, I noticed that the running application in the Windows Start bar changes to the new application. When I use the 'RUN /N' it runs outside the application creating a new item in the Windows start bar. Very interesting.