Thanks Greg, I may have to resort to that in the end. I've got data tables open etc and all sorts of things (none of which are causing me any problem) but would be hard to move over in a RUN)

>Hi David,
>
>I have one VFP exe running second using RUN command and it works well.
>I am passing veriables between two exe via dbf table.
>
>Gregory
>
>>That's what I thought, but even doing that doesn't seem to help. The .exe only gets 'bound' if I actually instantiate an object of a class in the classlib. So even though the object is released properly and I go
>>set classlib to
>>the exe is 'held on to'
>>Eric is suggesting running the second exe using RUN but there are variables and setting etc in the Shell.exe which the called exe needs to access.
>>
>>
>>>I'm not sure, but I think you have to tell the second exe to close its classlibs and everything else and to close itself.
>>>
>>>Vlad
>>>
>>>>This may appear unusual, but I have a VFP program which is a shell which will run another VFP .exe program.
>>>>
>>>>My shell code is roughly
>>>>DO WHILE .T.
>>>> IF ... && .exe has changed....
>>>> CLEAR PROGRAM
>>>> SET CLASSLIB TO && etc etc
>>>> .
>>>> DO (exename) && where 'exename' is the name of the new executable detected
>>>> ENDIF
>>>>ENDDO
>>>>
>>>>This all works fine and the shell program will fire up another exe without problem anytime I want except when the called exe contains a custom class declared in code.
>>>>I can still run the new exe but for some reason the previous exe stays held open by the shell prgoram. That is if I try to delete the .exe file that is no longer used, I can't.
>>>>If my 'exename' doesn't declare any classes I have no problems at all.
>>>>TIA