>I had a problem with one FoxPro DOS application (not mine). It used commonly approved scheme of getting unique IDs (lock the table, increment value, unlock) When moved to NT network (Token Ring) it started to give duplicate IDs. Using FLUSH didn't affect this behaviour at all. It was tracked down to NT server cache, but it was not possible to turn it off as other app started to fail after that.

I agree. In my testing of a similar problem, FLUSH only cleared the buffer, nothing more than that. It may only update a local temp file or server temp file, but not necessarily the server disk data. Only a full close/re-open of a table absolutely guaranteed updates were pushed to server disk successfully.

This is especially true of tables opened EXCL, where network optimization schemes may cause full copies to be made locally.