I'm going through hell at the moment with transactions and tableupdates reporting success, when in fact all changes just dissappear as if they were never made. This only happens on a few sites and is usuually traceable to a single workstation or 2 on the network. So far the 2 worst & most frequently having this problem, sites are a windows 2000 network and the other a Novell 5 server, with 3 WIN98 workstations and 1 NT workstation.( the NT workstation has the most problems). There has been a lot of talk here about this problem, with the main reply being to force a FLUSH command after the TableUpdate &/or END TRANSACTION. I have found that FLUSH does not always solve the problem.

(I even programmed a cut down version of my Merge & Update Program that tests the number of records in the file to be updated before the TABLEUPDATE and after the update. If the number of records had not changed then the problem had occurred. This is where i Tried the FLUSH command with only 50% success rate.

My advice to you (Finally he says) is to NOT USE TABLE BUFFERING.

Change to ROW Buffering, even though it means extra programming on your part. Ive seen where TABLE BUFFERING will ignore all changes being made but as soon as you change to ROW Buffering, every thing starts to work as it should.
(most of the time)