> > >>>>>>Are you sure the file is not really erased right away? What do you > have if you test it with FILE()? I also noticed some "bad behavior" of > Windows 95 Explorer on Netware LAN. > >>>>> > >>>>>The problem is that we show a list of files to download from our > Intranet applications. Once the user finish the download, we erase the file > because it has to be gone from the list of downloadable files. Since the > server is taking a while to react, the user can still click on it again and > this is not good. > >>>> > >>>>What happens if you do a manual Refresh on Explorer? > >>> > >>>Nothing, we have to wait about 30 seconds. > >> > >>Did you try also DELETE FILE command? > > > >I thought of that but I haven't try anything yet. It might also be related > to the configuration on the server which might cause this behavior. IAC, I > will try DELETE FILE on Monday. > > Michel, this sounds like a problem I had several years ago on a Novell > server. The (DOS) app deleted a file, but the Novell buffers weren't > flushed to the hard disk for seconds - and even minutes - so the file > remained on the server hard disk until the Novell software decided to write > its cache. We never found an answer, because there wasn't any way to tell > the Novell software to clear the write cache. :-( Check the documentation on the ODI driver (you may have to check support.novell.com). There's a timing setting about delaying writes (I can't remember the actual directive at this point) to reduce network traffic. It's got something stupid to do with the number of packets that you send to the server, I guess. IAC, I always set this to 0 or as close as possible, and I've not had any problems. /Paul