> Hello,
>
> Just a quick tip for anyone who is calling a VFP COM DLL from a .Net web service. When I was using the SOAP Toolkit to publish my web service, I had to give Write permissions to the IUSR_[machine name] account to update any tables from the web service, so when I created a .Net web service to act as the "middle man" to replace the SOAP toolkit, I assumed that the same would hold true.
>
> However, I found that when calling the VFP COM DLL from the .Net web service, on one server, I had to give Write permissions to the ASPNET account. Then, on a second server where I deployed the web service, I had to give Write permissions to the NETWORK SERVICE account instead. I figured out that it was running under that account by adding some code to my error handler to build an error message string that included SYS(0), which told me it was running under NETWORK SERVICE instead of ASPNET.
>
> I also found that when the folder that contains the DBF files is nested inside of another folder, I had to give Write permissions at the top level folder instead of drilling down and giving them Write permissions only on the Data folder. For example, if my DBFs were in a folder named C:\MyCompany\MyApp\Data, I couldn't just give Write permissions on the specific Data folder. If I did, I would receive a "Cannot update the cursor because it's read-only" error. However, if I set the Write permissions on the C:\MyCompany folder, it works.
>
> I hope this might save someone some trouble.
>
> Jon

Good one, thanks for the tip Jon. My rating to you.

Boudewijn Lutge®ink
http://www.vfpdevelopers-online.com
The truth will set you free, Ken knew the truth!