>>Wont it make your path statement fairly long and is there not a limit to th length of the set path to statement. E.G. L:\ becomes \\402fs1\data2
>
>I am not sure about that, but we are not talking about the OS path environment. I believe you are referring to the VFP search path. Each of my apps has its own VFP search path which I have never had a problem exceeding [it only needs at most 3 different search paths]. I do not use a search path to my DBC and tables because I explicitly include the path in my OPEN DATA command so the correct DBC gets opened. Once the DBC is open, I do not need a path to open the tables in the DBC. If I have any free tables I also include the path CONSTANT in the USE command.
>
>If you have a complex network system [multiple servers with multiple volumes per server], UNC will save you much grief. Everyone of our Divisions here want certain mappings and drive letters, and they certainly do not coincide with what other Divisions have. Now, I don't care what drive mappings users have because I use UNC exclusively.

I agree with you on drive mapping, that is why I have started to convert my drives to UNC, the users spread over different departments were using their own drive letters and they were also the ones I needed. This change will take care of that problem.

s for my VFP search path that is fairly long, but I intend to make it shorter by including more constants and have a table that stores system locations for me. Thanks for your time on this.