Bruce,
>> The question about FLUSH is, what is meant by "flushing to disk"? It may just mean the local copies in my theory, which is pretty much the same thing Tableupdate apparently does.
FLUSH just flushes the memory of the local computer to disk. "To disk" however can, and often is, not the real disk but *another* bit of memory, usually the disk cacheing controller on the file server. The latency there is usually only a second or so depending on controller and unless you want to "go deep" into writing a driver interface (not recommended) then you're stuck there. Again, that's _usually_ not a big problem.
>>What I'll probably end up doing is opening SHAREd for most editing work, and the one heavy data-processing section of the process where EXCL is required, do a separate close, open EXCL , process, reclose, and reopen SHARED afterward. It will require a little interface work, but is the easiest way to resolve it I can see...
Makes sense.
Best,
Best,
DD
A man is no fool who gives up that which he cannot keep for that which he cannot lose.
Everything I don't understand must be easy!
The difficulty of any task is measured by the capacity of the agent performing the work.
