After some digging, I found clireg32 and the automation DLL and stuffed them into my \system32 directory. Then I did 'clireg32 myapp.vbr' and selected DCOM. So I guess it's now registered. I guess that'll be something to add into my desktop app startup routine, no?



>>I think remote server DCOM support was added to VB 6 in SP3 with an additional parameter in CreateObject(). It was added to VBA, and VBScript 5 as well.
>>
>
>Right, but AFAIK, it still requires that the object be registered on the client, whereas with CREATEOBJECTEX, you can use the CLSID and instanciate an unregistered class (as long as it is configured to run on the specified machine).
>
>>Incidentally, CoCreateInstanceEx is pretty easy to implement at least in C code. I remember when I had to do this in Web Connection for remote COM object support and was dreading the whole deal, but it was surprisingly simple...
>
>The simple can become complex without the right set of tools. AFAIR, the problem in VB was getting an object reference from an API call. It took some pretty extensive trickery.