>>I wanted to thank you for sticking with my support issue. A while back you mentioned that I shouldn't have to keep the perms, dll registrations, file distributions, etc in check by myself. You encouraged me to use a program like activevfp to keep everything straight so nothing is forgotten or overlooked. You were absolutley correct. I forgot to bring over a meta table that tells the mtdll vfpcom object where the data directory is. I also forgot to set up perms correctly in one directory. I traced out how activevfp sets up the sample app and learned a great deal. The most important of which is that my vfp mtdll com object does not have to be distantly placed in system32. I see that activevfp puts it in close proximity to the rest of the application files. Once again, thanx and I will be using activevfp to set up my web apps in the future.
>>
>>Regards,
>>Dr. G. (Neil)
>>
>>>You could try it without messing with the virtual. You're right - it doesn't matter in relation to the mtdll once it's registered. If it still doesn't work though, after giving the new directory and files the proper permissions, then you may want to take a close look at the Virtual and the ASP script. I would match them up exactly to how they're configured in ActiveVFP..
>>>>I am clear on the new directory for the vfp dll along with the unregistering and registering procedures. But... why would I do I need to do anything with the virtual?
>>>>
>>>>Neil
>>>>
>>>>>Oh- the system32 directory could be problematic. I would create a new physical directory and a new virtual directory for it. Then unregister the mtdll, copy to the new directory, and register it again.
>>>>>This is a good reason to automate the mtdll setup with InstallShield or something so you don't have to go thru all of these steps every time.
>>>>>>That was a great idea to look at the way activevfp configured everything on my computer. However... everything checks out. I did lower the IIS pooling though for the virtual. Still no data access. BTW... since data is running on same computer as iis I deleted the COM+ setup. That did not help either. Do you think it might be something to do with the fact that my ASP's vfp dll is running in system32. That fact does not seem to affect my ASP.NET vfp dll's but it's just a thought.
>>>>>>
>>>>>>Thanx once again for all of your ideas but I am still in trouble.
>>>>>>
>>>>>>Regards,
>>>>>>Neil
>>>>>>
>>>>>>>Is the data on the same computer as IIS? If it is, there's no need for COM+ unless I'm missing something. Did you compare with how ActiveVFP is set up? You might even want to put your FPW2.6 data in the ActiveVFP data directory and see if you can access it. It should be something simple...
>>>>>>>
>>>>>>>>Thank you. I have IUSR_ and IWAM_ with full control to the dll and full access and launch rights in COM+. IWAM_ and IUSR_ have full control of data also. Still I cannot get to the FPW2.6 data tables without an error thrown by the ASP. The only thing that a changed since it did work was migrate to new computer with XP SP2 from a computer that had XP SP1. Could I be missing something in the way XP SP2 defaults the security?
>>>>>>>>
>>>>>>>>Neil
>>>>>>>>
>>>>>>>>>The 'proper' way to do this is to run your component under COM+ because you can configure the Impersonation for an (out of process) COM+ package. I say proper in quotes because although it works is somewhat of a PITA especially during development. During development I'd suggest you just give hte account running the request rights to access the data files. By default ASP runs under the inbound user account which is usually IUSR_ or whoever is authenticated if you have authentication set against your ASP pages.
>>>>>>>>>
>>>>>>>>>+++ Rick ---
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>windows xp sp2 is not allowing a mtdll, which I instantiate from an active server page, access to my vfp tables. It runs fine on windows xp without sp2. Can someone tell me how to set up the rights so that a vfp mtdll, that reads and writes data to vfp tables, so that it can be instantiated on an active server page. BTW.... I am running this on my development computer. The web page is being served up on the same computer that I am viewing the web page from. And.... what user is accessing the vfp mtdll when it is instatiated from an asp.
>>>>>>>>>>
>>>>>>>>>>Regards,
>>>>>>>>>>Neil