>>>Guess the ultimate answer is that we will never know how the VFPCOM crosses the COM boundries.
>>
>>Hogwash. :-) We just have to ask the right person. I'll corner somebody at the next DevCon.
>
>My assumption is that VFPCOM.DLL is written in C++ and somehow is able to access the memory registers that VFP is using to determine what file is open in the current work area or for the paseed alias. Something that a VFP programmer can not do, so we will have to settle for opening file again.
>
>BOb

See my response to David.