>Actually, I'v been putting more and more of my code into
>custom classes, then building them into DLL's so that I
>could swap out components more easily. So far it's all
>worked really nice. I was hoping to do the same with the
>data.

But if you are only using these classes from VFP, then they don't need to be COM srevers at all. You can still get all of the code reuses with a regular VFP class, and none of the overhead of COM.

Having a COM server open a table and making htat table available to the client goes against the spirit of COM, which is supposed to be client independent. All communication with the COM server should be through its PEMs- no tables, no global variables, nothing else.