Neil,
I thought you were also using impersonation with COM+ for the vfp mtdll?? This would allow network things to work.Not sure if you tried this or not. You might have to use DCOMCNFG for impersonated rights on the VFP COM EXE Server too.
BTW, Evan Delay developed a project similar to yours (I believe) somewhat recently. You may want to ask him...
>Hi,
>
>My asp.net application contains the following elements:
>
>ASPCOMPAT
>IMPERSONATION
>VFP MTDLL COM SERVER
>VFP EXE COM SERVER
>
>I am using 1 vfp exe com server and 1 vfp mtdll com server in an asp.net application. Although the mtdll is preferred, the mtdll does not permit use of commands such as REPORT FORM and INKEY(nn,"H") so I need an EXE com Server version for my vfp-.net interop project as well as a mtdll. I am experiencing differences between the 2 com servers in how they interact with my peer to peer network that is utilizing an impersonated user. The network has 2 computers. The web server, which hosts win 2k server and runs my asp.net web application, and a work staion running win 2k prof., which hosts my vfp data tables.
>
>My asp.net application is using impersonation so that I can access my vfp tables situated on the work station. I configured the work station, hosting the vfp tables, with a user named gmgOnLine and made it a member of the Administrator Group for now. I configured a user of the same name on my web server, which is hosting the .net framework and my asp.net. I set up the web server's gmgOnline user with the same privledges as an ASPNET user as per Microsofts specs. ..With minimal rights.
>
>The vfp EXE COM server has no problem issuing a command like:
>

>if Directory(“h:\Data\”)
>  do something….
>Else
>  Do something else…..
>endif
>

>
>However, the same exact command issued by the mtdll com server always returns .F. In fact,
>

>if File()
>endif
>

>
>fails just as well. Always returning .f.
>
>
>I am able to get around the mtdll com limitations by discontinuing the use of impersonation and falling back to an ASPNET user and placing the vfp data files back on the web server. I guess the impersonated user is missing the local security policy to necessary read the directory info. Or... maybe it has something do do with threads and where my ASP.NET runs COM objects. I find it confusing that the vfp dll is multithreaded but ASP.NET runs COM in STA. My mind cannot seem to wrap around the concept.
>
>
>Please note that I attempted to add ASPCOMPAT="true" to pages hosting my vfp COM objects but this resulted in a COM exception each time I my asp.net page attempted to instantiate the COM object. I found that I could leave ASPCOMPAT="true", and run just fine, if I come out of impersonation, put the vfp tables back on the web server, and use the default ASPNET user.
>
>In summary,
>I think the problem is somewhere in the impersonated user scheme of things. Any thoughts?
>
>
>Regards,
>Neil