>>Which is a better approach in managing database?
>>1. Pure Buffering feature
>>2. Combination of Buffering and BEGIN/END Transaction
>>3. Pure BEGIN/END Transaction
>>
>>What's the significance of Buffering feature in VFP when TRANSACTION can do what Buffering can?
>
>IMHO and i'm newbie coimpared to others, I do 2, I'll explain:
>
>Pure buffering don't gives you a security for the data. I use table buffering (5) and it inside a transaction.
>
>The meaning of transaction & buffering together is clear for me, think that a transaction must be as quickly as you can, it's no good to do the transaction of a grid, for this use bufering, and when the data is ok, issue a BEGIN TRANSACTION / TABLEUPDATE / ...
>
>I think anyone can explain yo this better than me.

Combination of the two is tricky especially when you deal with one to many relationship. I tried combining the two before but to my disappointment, it always gives me "Wait... Record is not available..." when two computers is executing the same module especially when saving time.

At click event of a button I have this code:

BEGIN TRANSACTION
blah..blah..

k = TABLEUPDATE(1,.F.,'table')
IF k
END TRANSACTION
ELSE
ROLLBACK
ENDIF

And so, my approach now is pure buffering:

=TABLEUPDATE(1,.T.,'table')

No more intermetent error. Everything is now running smoothly.
Just my own judgment, others may have better explanation to clarify this cloudy VFP feature.