>Hey all,
>
>We have a web site which uses a VFP database as it's backend data source. The web site connects to the data using an ODBC System DSN that points to a local drive folder containing the data. Works great.
>
>I tried moving the data to a different machine. Where before the ODBC DSN pointed to E:\QT2\DB\SYS.DBC (where E is a local drive on the web server machine), I changed it to point to J:\DB\SYS.DBC where J is a drive mapping to a different machine's shared folder. And now, the ODBC data source returns an error when the web page tries to access data, saying 'Cannot open file j:\db\sys.dbc'. This is absolutely not the case, as I can go to the very same machine and create a remote view (in VFP) utilizing the exact same ODBC DSN. How can this be? The _only_ difference between the working scenario and the broken one is that the good one uses the E drive (local) and the other uses the J drive (remote mapping). How can ODBC even tell the difference, and if it gets an error when gathering data for the web site, why doesn't it error out when getting data for a remote VFP view? I am at my wit's end...
>
>I would appreciate any help from the gurus...if at all possible, please e-mail me at sutekh@dwx.com, as I am still finding my way around Universal Thread and want to make sure I don't let an answer slip by...
>
>Thanks for your help!
>
>Joe Kaufman

You didn't say what mechanism you were using to access the data, but I suspect that the answer is the same regardless:
You need to make sure that the remote drive has read/write rights for the IUSR_ account. This is the account that IIS uses when accessing data as a result of a request. THe reason you are able to open the connection in VFP, is because you are opening it as a different user. HTH.