Chris
In the code in your Web Service, never use the mapped drives but use rather something like the following:

open database \\YourServer\YourShare\SomeDir\TheDataBase shared
*** then you can USE SomeTable ***
*** also, if you work without database and only free tables, use:
use \\Yourerver\YourShare\SomeDir\TheTable shared order blabla

HTH
Jaime


>I understand now about allowing IUSR_... access to my files.
>
>But my problem is way before that issue arises.
>
>I have my Web Service published on a computer, a server running IIS. Now when I manage that server (as Administrator or whatever), when I log in - either previous drive mappings are restored, or a login script runs. Consequently I have (say) drive S: mappped to a disk on a computer somewhere else in my LAN.
>
>I need to know how to set it up so that someone coming into my server from the WWW *also* sees that disk on a linked computer mapped to drive S: - because there is data on there my Web Service needs to fetch or update!
>
>Its all very well giving IUSR_... rights over that directory (while I am logged in as Administrator and am physically seated in front of the PC) - but how do I ensure that the IUSR... - the anonymous user making use of my Web Service from the outer limits of the World Wide Web - gets to see that disk in that networked comupter as a drive S: ?
>
>That user doesn't even log into the IIS Server, he just uses the web service, and he wouldn't want to wait for any kind of login process anyway - how then do I get certain drive mappings to persist - to be always "on", even when there is nobody logged in ?
>
>Thats what I need help with!
>
>Thanks for what you have contributed so far!
>
>Chris