>If TABLEUPDATE() fails, an error handler won't catch the error. You have to test it with AERROR() on the next line of code immediately following the call to TABLEUPDATE(). Then either commit or rollback the transaction.
>

The help file doesn't directly state, but implies that Tableupdate() will generate an error if nRows is set to 1 and table buffering is enabled. I have actually seen it set off my error handler before, so I know that it works.

Also, pessimistic buffering is only set on one table which I modify only through my "Finish" button. The click method will take care of calculations and bringing modified records from a cursor back to real tables. I have tried to stay with optimistic buffering for as long as I could, however, i'm running into problems with my inventory counts being wrong. Even with pessimistic set, I am still running into problems although it has improved.

would you know of any resources (samples, tutorials, real world situations, etc) that would help aid my understanding of locking/buffering/transactions etc.? I am **so** close to making this thing work but have run into some real stumbling blocks at the end.

TIA,
Jonathan Chan