Carmen,

Another approach is to use the SCATTER NAME command. Instead of using an array, it places the fields and their values in an object. For example, you can add a custom property to a form, and SCATTER NAME to that property, and GATHER NAME when you want to save the record.

But you still should look into buffering. You will find that you have more control over the buffering process if you use table buffering (rather than row). With row buffering, a tableupdate() is automatically performed by VFP when the record pointer moves. With table buffering, you tell it when to tableupdate().

I highly recommend Effective Techniques from www.hentzenwerke.com ...it is well worth the money and will help you make the transition.

HTH,

steve



>Using Foxpro 2.X, whenever I used a table in a multi-user environment, I would use an array filled with the scatter blank command to accept the data, then after confirming the information, a record would be added, and the information would be gathered into the table. I'm currently converting one of those applications, order entry, and finding it difficult to use the same approach. It seems difficult to use an array member as a control source for a text box on a form. Am I approaching this task the right way? When you use the table fields as the control source, it seems more circuitous to check for existing order numbers before saving, etc. Then if the user aborts the action, you have to unwind the whole process. Is there something basic that I am missing?
>
>Thanks in advance
>Carmen