Okay, it is not a code-access issue. And since other code is executing in the web application, it is not an IIS security issue. It sounds like an NTFS problem.

Is the DBF located in the same box as IIS? Does the IUSER_* account have NTFS permission to read/write in the DBF's directory and the default TEMP directory? I don't know whether the VFP OLEDB provider runs in a separate thread or not. If it does, what account is it running under, and does that account have rights to the DBF's directory and the default TEMP directory that VFP uses?

I'm sorry that I can't be more helpful. Perhaps someone else has worked through this problem and can be more specific.

>>Are you referring to IIS security or code-access security?
>
>Well, basically, I'm not sure presently where I should look to resolve the issue. What I know is that when I run this from http://localhost, it works ok. It can access the dbf from the OLEDBAdapter command. But, on the server, it cannot create a reference to the object. The directory where the Web Service is executed seems to have the same rights as any other Web Services I have built before. However, this is the first time I am accessing some data from it as usually I only use it as a wrapper.