>>While the OS takes some responsibility in this area, there are different ways to do the locking. I remember having problems with Clipper and FoxBase programs accessing the same data because the locking schemes are different.
>
>Hi Craig,
>
>That's true, but it was also back in the DOS days when an individual application had to take much more responsibility for what it did than they do under Windows. For example, off the top of my head, I can't think of any instance where a Windows based application handles its own I/O. It's all done through the API. The app just calls it, and the OS does the rest.
>
>Sort of in this area, I did some testing in regards to setting file time stamps using the API. I could set the modification date on a local file to anything I wanted. However, when I tried the same routines on a network drive, while the call reported that it had succeeded, the date/time stamp was unchanged.


My Clipper/FoxBase experience was on a Netware server.

Your testing in interesting. See my response regarding caching. This may be part of the reason you are seeing these results.