I just tried this on our Novell drive that has Long.nam loaded and enabled. Both files stayed intact with the code I placed in them. We are using NW 4.11, and my OS is also Win95 on this machine.

When I shelled out to DOS and did a DIR on these files, the one with the longer name displayed as an 8-character filename with the 8th letter replaced by a zero.

I alternated the MODI COMM between both files several times and experienced no failures.

Create a file with a long name on your network drive and see what the DOS DIR command gives you. Also try to verify that long filenames is implemented properly on the server drive[s].

>Root of the Problem:
>
> The root of the problem seems to be that when working on a network drive, any longname file can be accessed by either the full name, or the first 8 letters of the filename. The problem works as follows:
>
>Enter FoxPro
>type in the command window:
> modify command testfiledeletion
>A new program window comes up. Put any code into it, and save it.
>type in the command window:
> modify command testfile
>A new program window comes up. Put any code into it, and save it.
>
>Look in windows explorer and see that both files DO exist.
>
>type in the command window:
> modify command testfile
>A blank program window appears! Your code is gone!
>
>Look in windows explorer and see that testfile.prg has vanished!
>
>The O/S we are using here is Windows95 and we are on Novel system.
>
>My Conclusion from Data (?)
> The Network wants to be able to open testfiledeletion.prg by only the 1st 8 lettters (testfile). Since there is another file in existance called testfile.prg already, some confusion seems to be caused between foxpro, and an underlying system (seemingly the network, since this problem does NOT occur from the local drive), and the file with the eight letter name is gone!
>
>Can somebody comment on my conclusion and/or explain the cause of the probem?
>
>Thanks
>
>Slawek Lehmann