>When writing data to disk with tableupdate, triggers don't fire at the spected time, because update isn't done inmediatly.
>
>In a table with optimistic row bufferTableupdate returns .T., but data isn't written yet. It's wrote only after a second tableupdate or at the end transaction.
>
>What could be wrong?
>
>updating can't forced because I need to handle errors
>
>I'd appreciate any help


I would look harder at the Transaction processing. I do not think your problem is with Table buffering. Try looking at the MS KB articles or some other reference on Transaction processing.

Tom