Ok, i see now, and there is no way you can recreate the S: map from the machine running IIS ?

>I can open the database OK, using UNC or conventional paths.
>
>But I cannot open the tables without generating an error if the mapped S: drive does not exist.
>
>My database is located on Q:\ drive. Luckily for me that happens to be on the machine from which IIS (DEV-SERVER) is running (i.e. a share mapped to a drive), so I can open it wither be OPEN DATABASE S:\HFISH\PRO65\PRO65\PRODATA.DBC, or by OPEN DATABASE \\DEV-SERVER\CUST\HFISH\PRO65\PRODATA.DBC.
>
>No problems so far....
>
>However the TABLES that the database manages are on a different drive - normally mapped to drive S:, which is physically on a different machine - named SHIVA. I have deliberately broken my link to this (normally mapped to S:\ drive) to demonstrate the problem.
>
>Then with the database open I can open one of its tables (ARCUST01.DBF) in one of 3 ways:
>1. USE ARCUST01 - this generates an error: "File s:\hfish\pro65\ardata\arcust01.dbf does not exist"
>2. USE \\shiva\custdata\hfish\pro65\ardata\arcust01.dbf - this generates the following error: "q:\hfish\pro65\prodata.dbc: Cannot link table "\\.. \arcust01.dbf" to this database: duplicate or missing fields. Would you like to try to locate the owning database or delete the link (and free this table)?" - NOTE THIS HAPPENS EVEN IF DRIVE S: IS CURRENTLY AVAILABLE.
>3. No, can't do this becase I don't have drive S: mapped <g> - but if I did have it would open the desired table perfectly: USE S:\HFISH\PRO65\ARDATA\ARCUST01.DBF.
>
>You see, the DATABASE has references to the tables as belonging in directories of S:\ drive, so any use of UNC is worthless until such time as S:\ drive is found to be mapped, and even then its not much use if dealing with tables in a database....