Hi

Ok, my case is weird, so bear with me on this one. Here is what I try to do: via view the user is gonna be working with a record set, he will be able to update, delete and insert records.
Very often he is gonna be filtering the record set, each time he decides to reduce or add records through the filter he can't be forced to save the changes, instead the program got be able to keep the changes apart, so if the user the decides to see again the unfiltered records he will be able
to see the old unsaved changes and being able to save them anytime.
The only idea I came up with to solve this is that before applying the filter I should add the changed records into a cursor, revert the view and once I need to requery or refresh the view put back the changes into the respective records.
So I'd like to know your opinion on how to make this process the most efficient possible or implement a better solution.
For instance, wha is fastest way to know if there changes in the view.

Thanks in advance