Actually, MTS...

Well I found out what was wrong... but a little confused by it...

The first com object I created was from a VCX, the object was subclassed from custom. I compiled it into a COM object and loaded it into MTS, For the Identity I keyed in the Administrator of that server... But the Administrator was local so it does not have access to the other servers in the domain...
When I logon to this server, I logon as Administrator, and then when it trys to map to drives on other servers, I key in my Domain user account and password.

Well in any case this COM server worked... Then for some weird reason I wanted to do the same thing but create the object in a PRG... So when I was done I tested it as a regular object and everything worked... So then I compiled it into a COM server and loaded it into MTS, same way as above... And I started to have this annoying problem...

But then last night I had an idea, after my morning meetings, I went and changed the Identity in MTS to my domain logon. And guess what???


It worked...


I'm wondering why it did not affect the VCX class compiled into COM, but did affect the PRG class compiled into COM...

Weird...


Thank you to everyone who offered help...



Mike

>>I create the same class up above but in a PRG file instead of VCX. Same code and everything. And the class works. However when I define the class public and add it to a project and compile to a com server, the same code(that works in the VCX, and works as a regular VFP6sp4 object now generates an error. The 'load_data' method calls "open database f:\wrs\data\wrs.dbc shared" will throw an error. No where else does it throw an error but from the PRG file compiled into a COM server.
>
>Have you compiled the vcx into a COM server? Have you been playing around with DCOMCNFG?