>>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.

Yes, EXE run with "DO" command runs in the enviroment of the calling application. It has access to all varables, tables/cursors, etc. visible at the poinrt when it's called. It also means, that called application can change them or create/add new once and the changes will not be los when it finishes.