>>>In addition to what others have said, you can use sys(5) to pickup any user's drive letter, then add the rest of the network path, which should be constant.
>>
>>The thing to keep in mind, in my opinion, is that once you are addressing disk space other than local drives, drive letters are at best a handy shorthand - the more accurate and (hopefully) unchanging notation would be the UNC notation.
>
>
>David,
>
>Sorry, I'll have to take the other side on this one. The reason being that we just changed server operating system versions. Among the things that changed were the volume name of the servers, which changed the way they're addressed. Had my applications not been setup to look for the drive letter path combination, there would have been many hours spent re-writing and debugging. As it is, I've had to do nothing to deal with the change over.
>
>BTW, I grew up on the South Side, around the University of Chicago. And I sure could go for an Italian Beef right now. :-)

I agree with George on this one - last week we installed new server with new server/volume names - my apps use ADIR(laVol,lcDrive+":\",'V') to return the server/volume name and checks this against a table in my project. I had to change all the projects which used this format! This, however, was the only flexible way I could think of to use networks.