I'm more and more sure this is a networking problem, although how it works in VFP6 is beyond me. Quicky network explanation:
Novell breaks disks up into logical volumes, there is always a volume named SYS: and others at at the whim of the network admins. That volume roughly corresponds to, say, the C: drive in your PC. Under there, you create directories, just like on your local hard drive. On the network, you map drives to represent these directories, in Netware the command is MAP as Tracy said. Now, say your disk looks like this:

SYS:
    |
     -HOME
    |
     -PROGRAMS

You use the MAP command to connect a drive letter to one of those directories, such as MAP H:=SYS:HOME, now when you select drive H:, you are in the HOME directory. Likewise, you might MAP P:=SYS:PROGRAMS. If you select drive H: and issue a DIR, you see all files you have rights to in the HOME directory. But here's the tricky part - with Netware, you can type in something like DIR H:\, and what you would see is the HOME and PROGRAMS directories. This is the equivalent of being in C:\WINDOWS on your local computer and typing DIR C:\, you see everything in the root of the drive. This is why, in this example, SET PATH TO P: and then issuing USE \MYAPP\MYTABLE.DBF is NOT the same as USE MYAPP\MYTABLE.DBF. They seem alike, but the leading backslash means relative to the root of the drive. Yes, it's confusing somewhat, but read carefully. The problem is, nothing forces the drive letter to point to what it was originally mapped to. There is a solution, Novell offers a variation on the MAP command, MAP ROOT, ie MAP ROOT P:=SYS:PROGRAMS. If MAP ROOT is used, it prevents moving to a higher level directory. With MAP ROOT, DIR P: and DIR P:\ would be exactly the same, because it prevents looking higher in the directory tree than the PROGRAMS directory. With MAP ROOT, doing the SET PATH TO P: and then USE \MYAPP\MYTABLE.DBF and USE MYAPP\MYTABLE.DBF would be functionally equivalent.
OK, I'll let you digest that for a while - it's really not too hard to understand. I'm just suprised that VFP6 would work ok, personally, I would expect the behavior you are seeing, not have it work. This isn't an issue with Microsoft networking, as the equivalent to the MAP command (NET USE) has an implied MAP ROOT, ie, all drive mappings in NT are MAP ROOT.

Randy
>
>I'm doing this right from the command window. Both drives are mapped to sub-directories on different servers.
>