Yes, this happens when you run the EXE/APP (BTW MS advertise this as a feature, and I agree with them), but if you use COM the com runs under its runtime libraries. I just tested this on my computer with VFP8 and VFP9.

>Running a VFP 7 executable from another VFP 9 executable will force the VFP 7 executable to use the VFP9 dlls. Been there, done that, recompiled VFP 7 app into VFP 9.
>
>E.G.
>
>VFP 9 EXE ---> VFP 7 EXE
>VFP 9 DLL ---> VFP 9 DLL
>
>VFP 7 EXE ---> VFP 9 EXE
>VFP 7 DLL ---> VFP 7 DLL
>
>
>I didn't like this either.
>
>
>>>I'm afraid you are right Borislav :-(
>>>the strange is that i get no error when I build the object !
>>>
>>>thank anyway, I give up :-)
>>>
>>>>Headers always had Click event, but I am not sure if VFP7 can use custom column and header class in Grid. If I remember correctly they were introduced in VFP8.
>>
>>Why you start VFP9 routine from VFP7 one?
>>Unfortunately I have no older versions here installed to test, but how you started this anddid you expect somethind to be returned from this routine?
>>Can you build a VFP9 EXE as COM server and use COM object reference in VFP7 instead of running routine?