I've tried creating a second view of the first view with the intent of putting table level buffering on it instead of row, but it keeps returning all the records from the base table instead of those that are in the first view. The first view is based on a table and has the social security number as its criteria, so I thought that the second view, with no criteria, would pull only the records contained in the filtered first view, not all the records as if there was no criteria at all. If I need to have criteria on the second view, then I can't use it for this purpose. What fundamental understanding am I lacking on this? Thanks!

>The nature of the beast on this application requires me to allow editing of a field that is used as the selection criteria for a grid's view. For example, on a grid on a form the user selects a record and second form appears with a grid. This second grid is based on a view using the social security number from the selected record as it's criteria. The point of this second form and grid is to allow editing of the social security number. It is not allow anywhere else in the system, but the user needs to be able to do it from time to time. The problem I have is after the field is changed and Save is selected, the subsequent TableUpdate causes the view to display all records except the one that was changed. I understand why this is so, but is there a logical way to save the record and have it appear in the grid at the same time? I'm thinking something about two views, one based on the other, but it's getting a bit murky the more I try to think about it... Any help is greatly appreciated...
>Thanks!
>
>Regards, Renoir