>I would like to know what is people using and why when designing forms:
>1. The m. approach: in which all textBoxes have memory variables you get with a SCATTER MEMVAR, and when you save changes you make a GATHER MEMVAR.
>2. The new tableUpdate() approach: in which you are constantly reading the table itself in the textBoxes, and make a tableUpdate() or tableRevert() when making changes.
>
>I think the second approach is more professional and flexible, due to buffering capabilities and modes. The problem is that when I add-change a record in some tables, I check a lot of information and I have to go through the table several times. If I do so, I loose some of the advantages of buffering when set to record-buffering.
>
>Comments and experiences are more than welcome.
>Regards,

Javier

TableUdate() most of the time if not always. Use scatter/gather if you have a set of data you wish to keep in memory for reference -- Use the new NAME option to stays OOPish (s). You also have OldVal() & CurVal() you can play with.

Tom