Hey Victor,

Yeah, calling a different version VFP app from within another may cause issues. I don't recall the exact technical details but I did test this scenario at MS and I believe it's because the called VFP app looks for the VFP runtimes to be loaded and it doesn't check version. It's just happy that there are runtimes in memory.

Also what could be a factor is the default version. VFP looks primarily for whatever the last version installed was in the registry.

>>There is a class that I need to create a service that is only available in VFP9. It will send/recieve info using ports. There is a VFP8 application that will also communicate using these ports. Any issues having the service created in version 9 with the app in version 8? Thanks!
>>
>>UPDATE: It's not the ports that I'm concerened with, but rather running VFP9 and VFP8 on the same box. Or any other issues anyone can think of.
>
>One thing I stumbled acorss once - if you're running a VFP8 app and then call a VFP9 app from within it - the VFP9 app actually uses the VFP8 runtimes.