Update:

All issues are resolved with the exception of the mapped network drive access part, which I can do without, since the intended use for this component is to place it on the server the data will be local to.

I implemented COMRETURNERROR() and moved certain initialization code to a different method, since errors in Init can't be passed back through the COM mechanism, likely due to the component not being fully initialized at that point. That's how I found out what the issue was with the mapped drive.

I set the component to impersonate my own user account which has admin rights to everything. It still won't access network resources, but I get no 'access denied' events generated, etc. It occurs to me this component is essentially getting it's own login session and perhaps the drive would need to me mapped within that session, so to speak. It is behaving more like the drive mapping is non-existent, as opposed to being denied access to the network.

I found out enough about the Component Services snap-in to be able to administer the COM+ app, so I am fat and happy at this point.

Thanks again for all the help and support. :) I'm now on my way to accomplishing the actual task intended for these components.



>What security ID is the component running under?
>
>You can use a text file or the Windows Event Log.
>
>
>>I found that out, also. Thanks again. Now I can kill them when they die easily enough. Now I seem to be having a problem accessing a mapped network drive from within the component, as best I can tell. The code works fine if invoked as a regular VFP class locally.
>>
>>
>>Event : "The redirector failed to determine the connection type."