Hi Vlad,

I guess I could put the Flush after the critical table updtes. I was a little worried about slowing the system down too much but a little slowness is better than losing data.

Also, I could not find the switch for the write-behind buffering. Could you be a bit more specific. Is there any documentation on that?

Thanks, ken
>
>Use FLUSH command for this after END transaction (or tabbleupdate() if you do not have a transaction).
>
>In addition, check system settings - there is an option to switch off write-behind buffering. This will slow down the system a bit, but data writing will be much better.

>This also might be a network issue - could not help you here much...
>
>>I'm running a system on a small W98 Peer-to-Peer network (4 workstations). Not an ideal but that is what I have to work with. Thing is on two computers I have been losing data from buffered views. I haven't figured out why but think that may be a temporary or partial solution would be to flush the data to disk more often than the automatic flushing (5 minutes?)
>>
>>Can anyone give me ideas on this?
>>
>>TIA,
>>Ken