>Hi all,
>In one of my client's deployment of our accounting application, ( 4 XP Prof PCs networked), there was a power failure recently and I was surprised to find that the day's transactions keyed in by the staff completely went missing or some were orphaned. (ie some like sales invoices went completely missing while others, posted to accounting ledger files but the transaction missed out in some of the sub ledgers).
>I had noticed that these transactions were keyed in quite some time (at least an hour ) before the power failure from different terminals). Some of these transactions were even edited before in the individual PCs. ( the client was able to retrieve the records for editing from the terminals that was used to key in ).
>What disturbs me is that I get the feeling that the records were saved only in the cache of the individual PCs but were never written into the PC that's acting as a "server".
>In my code, I use remote views for data entry and all inserts into other tables are wrapped in a complete begin transaction/end transaction cycle with rollback for failures. After each save, flush is issued.
>I had noticed on several occasions that records saved in one PC cannot be seen at all by another PC until the other PCs does an append or something that forces an update of the record pointer.
>I've set refresh to 5,5 or shorter but to no avail.
>Hope there's clues how to debug this.
>Thanks in advance.
>Yau

did you try SET REFRESH to 1,1 ?
something else that might work is to move the record pointer off and then return to it,
ie: nRec=recno() , go top , go (nRec)
maybe locking and unlocking the record would help.
There is also SET AUTOSAVE that might work for you.