Well, are you accessing vfp data across the network or using SQL/MSDE? These have been the primary uses for COM+ that I've seen. If these aren't requirements, then no, it probably isn't needed...
>Hi Claude, sorry to drift off topic...
>
>I've never put my COM DLL's into COM+, but have simply registered them on the server and referenced from from my ASP.NET on my app. What realistically am I losing by doing this?
>
>>DCOMCNFG is something you don't need for VFP MT COM (thank god!). Use COM+ instead - here are some simple instructions that don't seem to be documented anywhere (at least for VFPers):
>>COM + Setup Instructions for a VFPmtdll on Windows2000
>>1.)go into Control Panel, Component Services
>>2.)right click COM+ applications and select New.
>>3.)going through the wizard, create an Empty Application,giving it a name, check server application, and select the appropriate account to run under.
>>4.)After the Empty Application is created, right click on 'Components' under the newly created application.
>>5.) select New/Component.
>>6.) The wizard starts - select 'Import components that are already registered.'
>>7.) select your Visual FoxPro mtdll from the list and it is added to this COM+ app.
>>8.) right click on your COM+ application name and select 'Start'. The COM+ icon is now revolving in the Components pane.
>>
>>>Hi all,
>>>
>>>I have created a VFP MT COM namely "busobj.eaccess" that accesses my database. I have tested it with CreateObject from VFP command window and I get the desired results.
>>>
>>>I have also created a (using C#) ASP.NET project which is intended to consume the services of that VFP COM. I added the COM as a reference in the ASP.NET project then imported it into the webform that will consume it as follows:
>>>

>>>//other using omitted
>>>using busobj;
>>>namespace mywebapp
>>>{
>>>  public class myform : System.Web.UI.Page
>>>  {
>>>    protected eaccess oea;
>>>    private void Page_Load(object sender, System.EventArgs e)
>>>   {
>>>     try
>>>     {
>>>       oea = new eaccessClass(); // fails
>>>     }
>>>     catch (Exception ex)
>>>     {
>>>      //ex.Message says Access dennied
>>>     }
>>>     string lcxml = "";
>>>     if (oea!=null) lcxml = oea.MyXmlList();
>>>     // code omitted
>>>   }
>>>  }
>>>}
>>>

>>>When the code runs to the line "oea = new eaccessClass();" an Exception is thrown and the message says
>>>"Access dennied". Through DCOMCNFG in the component service, I had given the internet user iusr_machine launching and accessing permission.
>>>
>>>When I viewed the busobj reference in the Object Browser in VS.NET, I could see all the methods.
>>>
>>>How can I fix this?
>>>
>>>Any help will be greatly appreciated,