I think you're misunderstanding the situation. The user has made changes (perhaps quite a few) to a child table (a view) that is displayed in a grid. They then attempt to save the record and during the save it says that they can't save because "the cursor cannot be modified because it contains uncommitted changes." Well, yes, it does contain uncommitted changes. All of which need to be saved, but instead I get this error. I can't TABLEREVERT because the user has made changes with the intention of saving them, not reverting them. It's like saying "sorry, you've made changes therefore I can't save your changes - you'll have to revert your changes, make them again, and then maybe I'll be able to save them next time."
For reference, see thread #
787471 that Sergey referred me to. In that thread you are answering the exact same situation and offered a workaround that I'm looking into. By the way - the "this is by design" comment that you offer in that thread is not very reassuring. If this is by design, it is poor design that hinders our use of VFP.
Thanks again,
Russell
>Hi Russell,
>
>If you are using table buffering then what problems do you have with saving the record (the workaround) ? If user decides to cancel the modification, just execute TABLEREVERT for the record.
>
>Thanks,
>Aleksey.