>>>>I have a form I need to revamp that uses multiple views based from a single table. There is a grid populated by one view. Some processing will occur that will involve scanning and switching between views and moving/copying records depending on flags that are set for the records displayed in the grid. There are no relationships between the views. I plan on using Table Buffering and am having a hard time getting my mind around how I need to handle the adds/deletes/updates for the different views. Is the best way to make all changes to all views then do the updates on the individual view? Is there a better way or more accepted way? This is new to me as I normally have only one record to update at a time and I have a oApp class to handle it as needed. Thanks!
>>>>
>>>>Regards, Renoir
>>>
>>>Renoir,
>>>Multiple views or multiple instances of same table or multiple users of same table. They all could be seen as same IMHO.
>>>PS: If only from a single table wouldn't it be easier to work directly with the table itself.
>>>Cetin
>>
>>Cetin,
>>
>>Maybe so, but the logic is that there is a field in the table and it's value determines the contents of each view. When working in the MyMain view, based on a flag I might need to take a record from the MySecondary view, compare it to a record in MyTertiary view and then move/copy the record back into the Main view. It seemed that the easiest way was to have separate views.
>>
>>Renoir
>
>Would transactions be a good solution for this issue?
>
>Renoir

I don't know, couldn't get the scenario. I wouldn't use multiple views (or a single view) on only one table. Instead I would use the same table n times with different aliases if need be.
Cetin