>>Hi Cy,
How do you search the table without the new record being part of it. It seemed that when I had the text box control source as a field in the table, it would always find it as a table record thus causing problems on every transaction.

Regards
Carmen

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?
>
>What your doing is a good candidate for using views and buffering. That way you can search in the base table for duplicate keys, without affecting the view, and if the user cancels just do a TABLEREVERT and do a TABLEUPDATE to save. I find this works quite well, and after you get used to it, it's actually easier IMHO.