David,

Thanks for the help.

Just trying to come up with an example to be sure that I understand the reason for a p-view without a parent child relationship. If the form presents several records like all the chili from New York City your parameterized view would be based on the chili table and all the records from New York City and you would view/edit all those records. This would use table buffering.

>John,
>
>If I've got a form that's just editing a single record I row buffer the table. If I have a form that presents several records I normally use a p-view table buffered. If I have a parent-child form I row buffer the parent table and table buffer the child p-view. That covers 99% of my forms, the other 1% are too odd to use any general rule. *s*
>
>>Thanks for the input. I think that I see now what I was missing in buffering. If I use row buffering it is only while I am on that row. If I use TABLE buffering I can move about and edit or add and still do a tablerevert. Do you have any general rules that you follow about using buffering?