If I give permission to "everyone", insofar as the tables and the folders holding VFP tables, then things work OK. So the problem is definitely related to permissions, and for some reason, Mr IUSR and Mr IWAM just don't carry the stature they used to, because giving them full permissions to the VFP files (and the folders containing them) won't work. In fact, we found a puzzling key requirement: The folder containing the DBF file must be readable by members of the built-in group "Users", or else the app comes back with a DBF-doesn't-exist error. Even if you give full access to the IUSR and IWAM identities, it won't work.

>I would start by eliminating ODBC and just use ADO.
>
>>We are having a tough time getting the same kind of connectivity from ASP to VFP tables under Windows Server 2003 that worked fine with Windows Server 2000.
>>
>>We are running into problems with "internal server" errors and this error:
>>

Microsoft OLE DB Provider for ODBC Drivers error '80040e37'
>>[Microsoft][ODBC Visual FoxPro Driver]File 'xxxxx.dbf' does not exist.

>>even though we know the file exists.
>>
>>Can somebody help? I cannot find any documentation on how to use the VFP ODBC driver from ASP under WinServ2003. We need to know things like: how permissions need to be set on the VFP files (DBF, FPT, CDX), which security context is actually in place when the ODBC driver is executing, how to configure an IIS virtual folder (application) for an ASP app that uses the VFP ODBC driver.
>>
>>Thanks very much.