That makes sense John, Thanks. I've put this into use on a form and it's working well. I have two other questions on views...

1. I have a delete button and try to delete a record in the view then do a tableupdate of that view. Should that delete the record in the base table? It isn't in this case??? Is there something else that must be done to delete a record in a view and have that delete carry through to the base table?

2. When designing forms which are primarily based on a view, how do you then display "child" records? Do you put the child records in a view of their own parameterized based on the current record in the parent view? For example, my first view is customers. Now I want to add contacts information for each customer, like in a grid. Is is best to create a vContacts view with a parameter based on the customer key? Or is there another, better, way?

Thanks to everyone who has been contributing in this thread, it has been very helpful!


>You have to do two TABLEUPDATEs because you have "double buffering." The view >is buffered and the table is buffered. When you do the
> TABLEUPDATE() on the view, it updates the buffer of the table. You then have >to do TABLEUPDATE() on the table to commit the data in its
> buffer. When you close a table any changes are automatically committed. That's >why close and opening everything caused the data to show up in your
> view. The reason REQUERY() was working is that views only pull data from the >committed data in a table, not from the buffer.

> This probably isn't necessary. Unless you have a situation where you're >sometimes modifying the table directly and sometimes modifying the view you
> should turn off buffering on the table. That will save you from doing the >second TABLEUPDATE().