I described the scenario incorrectly. The problem occurs when the user exits the grid (which is located on a page) by clicking on another page tab. What event would fire in that case so that I can do the tableupdates at that time?

I realize I can put the tableupdates in the click event of all the other pages of the pageframe, but that seems inefficient.

There is no "close button" except the form itself.

Joel




>Joel,
>
>I've only come into this thread on the message below. However, I
>assume that you have a Valid() event for your grid. If that is the
>case, get your CLOSE button's Click() event to run the grid's Valid()
>event.
>
>It's simple and neat in that you have your validation code in only
>one place in this way.
>
>In simplest terms view Event code as no different from UDFs. In other
>words you can call a UDF in any part of a FoxPro program; similarly,
>you can call an object's event, provided it is visible, from pretty
>much anywhere else too.
>
>Regards,
>Michel.
>================== Your original message follows =================
>
>>Thanks Barbara and Sylvain,
>>
>>Yes, you were both helpful. Thanks. Now my work with views has encountered a new question. I have a form with a pageframe, 5 pages, each page has a grid. When the user starts on page one, he selects a customer which determines the cCustno which is the parameter driving the SQL views which appear on the other pages. The user can edit or append new records to the views, which in turn update their respective base tables, as long as I put the tableupdate()'s in the right place. That's where I'm having trouble. If the user edits a record in the grid, but does not change row or column, then exits the grid with the close button, I can't seem to determine which event to put the tableupdates in to ensure they fire before the user moves on to another customer.
>>
>>I guess this is no different that the same scheme with no views involved. Just exiting a grid with the close button. Must be pretty basic stuff.
>>
>>Thanks,
>>Joel