>
>The explanation is that FoxPro 2.x was written before UNC existed, and doesn't know about it. As far as FoxPro 2.x knows, \\server\share is an invalid path.
>
>Similarly, as far as FoxPro 2.x knows, longfilename.ext is an invalid filename. Although in the case of the long file name, FoxPro 'conveniently' 'fixes' the file name for you, and looks for longfile.ext instead, and probably gives you a file not found error instead of 'invalid file name'.
>
>One of the reasons to recommend for your clients to upgrade their systems to Visual FoxPro.
>
>HTH,

I need to butt in here. FoxPro 2.6 DOES recognise UNC - certainly in the most common commands. The problem may be that a connection has not been initiated to the server/share. If NetWare is used here, the server needs to be listed in the search drives in the login script. If NT, the user needs to be contained in the domain. The same problem occurs in VFP - try ?FILE("\\server\...") without first making a connection to the server. Then connect (via explorer) and try again. The long file name is an issue and (I just remembered) if the server or share name is over eight digits - that will fail using UNC.