You might try this question over at west-wind. I would point you to Rick's VC++/VFP article, but it doesn't address registration...

>I've gotten a VFP COM object up and running being called from a testbed VC++ program on my box which is Win95.
>
>I take the DLL, put it on an NT4 box, register the DLL and then try to use the COM from that code and the deep in the ATL bowels code hr = CoCreateInstance(rclsid, pOuter, dwClsContext, __uuidof(IUnknown), reinterpret_cast(&pIUnknown)); throws back an HRESULT of 0x80040154 which according to the winerror.h file is:
>
>// MessageId: REGDB_E_CLASSNOTREG
>//
>// Class not registered
>//
>#define REGDB_E_CLASSNOTREG _HRESULT_TYPEDEF_(0x80040154L)
>
>Anyone have an idea what this is really telling us?
>
>The really odd thing is it has worked once and we got an diagnositc message back from my code in the COM. I tweaked the COM to add some additional data to the message and now the VC++ gives the above problem. All we did was to copy the new DLL, register it and try to run it again. The DLL signature is in the registry and the code prior to the CoCreateInstance is finding the correct uuid for my COM and passing that rclsid into CoCreateInstance. Is there something more to getting a new DLL onto an NT box?