>>I know you dont want a lecture, but you are aware that table buffering does not prevent you from treating it - programmatically - as if it was row-buffered I hope.
>
>Jim,
>
>Interesting... I may not be aware. Do you mean using the nRows parameter in the TableUpdate while the buffering is set to table?
>
>Renoir
Sure. Update only the current row. And make sure it is TableUpdated before you jump programmatically to another record.
What your client probably wants is
not to have pending updates with more than the current record - you can achieve this with row buffering, or with table buffering. Table buffering avoids the unsolicited TableUpdate(). I remember this was my main compatibility problem when changing from VFP 3 to VFP 5 - I didn't have problems with VFP 3. The problems were solved, precisely, by applying table buffering.
Table buffering does have its own set of problems, though. If I remember correctly, you can't create a temporary index (IDX) on a table-buffered table.
Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
