>>Hey Ed,
>>FYI, VMP is designed to handle double buffering with no problems. The Save logic cycles through all open views and tables (in that order) twice. The first pass tableupdates the views to the underlying tables. Then the underlying tables are tableupdated. The second pass is to take care of any views or tables updated by any triggers run during the first pass.
>>
>
>Thanks, Larry - I remember struggling with it under VMP 3, which I used to derive the framework I use now for myself, and life became much simpler removing direct buffering of tables and using pviews for all Form activity.
>
>Wouldn't you actually need to refresh the view in the Save logic between the first and second pass to catch any triggers that insert or delete in related tables fired at the table level? I'm thinking of an example where a trigger of a child fires an action against a parent, and the view tuples include fields based on fields of the parent?
>
*snip*

One minor change to what I posted earlier that takes care of this scenario. The mulitple passes are only done to the tables. First the views are tableupdated and then the tables are done twice.

It makes sense because why would you make changes to a view in a trigger. *s*