>My suspicion is its the TABLEREVERT() that causes it. I have also experienced a data-bound control become 'readonly' after a TABLEREVERT() because of it reverted to an empty table.
>
>Also experienced 'readonly' phenomenon when logged in user has no rights on the particular table.
>
>HTH,
>Dennis
>
Do you have a solution for this problem?

We get a data into cursor using SQLPassThrough. Then we make this cursor updatable using the technique similar to outilined by Vlad G in the FAQ.

I'm wondering if issuing TableRevert somehow makes this cursor non-updatable? But why then clicking around makes it updatable again?

UPDATE. Making it updatabable again didn't solve the problem. However, refreshing the page after cancel helped. I commented out moving to another page, though. I'm going to test it now with moving to another page.