You're looking at several separate issues here...

If you stick a COM component into MTS/COM+ that component will run under the assigned user context and require the security priviliges you set up for that component. By default I think COM+ components run for all users no problem.

A plain DLL COM component also should work for all users although it may depend on where the DLL is located and whether the user has access to load and execute the DLL from there (same is true with COM+).

The issue with Word is that all COM objects must be manually configured to run under a certain security context. You use DCOMCNFG to do this. By default the rights on DCOMCNFG are very strict - but you can set hte default access rights for all DCOM objects on a machine in the generic security dialog.


+++ Rick ---


>I created a multi threaded COM DLL in VFP7. Some of it's functions contain automation, for example to Word. Now the COM has to be installed on a Windows 2000 machine (without VFP7). This is where the trouble started. I tried both ways I can think of
>
>First with MTS through the Component Services wizard in the Configuration Screen There I had no problems using the COM, also the Automation part, but ONLY as an Administrator, no matter the choice of user account (specific or interactive). This is not what I want. The COM also (maybe just) has to be available for a so called common user, so a non administrator one.
>
>Alternatively I tried the old fashioned way of registring by REGSVR32. First I registered the VFP7T.DLL (which is put in the WINNT\SYSTEM32 directory together with the VFP7RENU.DLL file). After that I registered my COM. The user account issue discribed above disappeared, but now it seems I cannot use the Automation part anymore. At that point the COM generates an "1426 OLE error code 0x80070005 Access denied" on the "oWord = CREATEOBJECT('word.application')" command.
>
>My question is: which of those two variants I should preferrable use and how do I solve the particular problem within that variant? I also have a (I guess) simular problem with the Outlook Automation for sending emails.