>>The DLL is like a separate instance of VFP. That's why the cursor doesn't go to the host program...
>
>It is - but some things aren't quite so separate.
>
>Just ran into a bug (MS calls it a feature) that when you SET DEFAULT TO in a
>VFP COM object called from a VFP COM client it will change the path for both
>the DLL and client.
>
>There may be other globals that do the same...
>

Whoa. Come again? This is a feature? I don't get it. It seems to me that a COM object is, by definition, separate from its host.

Out of curiosity, did you try the same scenario with the COM server as an EXE? I am curious if the fact that a DLL is inproc as opposed to outproc...