Are you building DLLs? If so those aren't remotable via DCOM. You'd have to build an EXE. However, I'm not even sure if you can remotely invoke even an EXE because I think the way COM on .Net objects works is that it works through a Proxy that calls into the native .Net class. Unless there's some special plumbing (which I don't know or think there is) these object will not be DCOM capable.

That said your only option will be to use COM+ and register the component as a COM+ component and then follow directions to expose an object for remote access that way.

+++ Rick ---


>Hi,
>
>I have a VFP 6.0 application running on a local machine.
>I need this application to access .NET classes residing on a server.
>I have compiled the .Net classes into COM objects, given them a strong name, used tlbexp, regasm and then gacutil on the server. No errors were received only messages saying registration was successful.
>
>I then try to access the component from my local machine using the following VFP code:
>
>oJob = CREATEOBJECTEX("{0345AE2B-9A1E-4C07-A7BD-DD874EBCBFD0}","\\Server01")
>
>where the first parameter is the CLSID on the server and Server01 is the server name.
>
>The error I get is "OLE Error Code 0x80040154: Class not registered."
>
>I have tried registering on my local machine and using:
>
>oJob = CREATEOBJECTEX("{0457AE2B-9A1E-4C07-A7BD-DD874EBCBFD0}","")
>
>This works fine.
>
>This application has a number of users and I don't want to have to register the COM object on every machine locally. I just want it on the server.
>
>Any help greatfully received.
>
>Regards,
>Roger Smith