Hello everybody,
I was wondering if somebody can explain to me the following behavior:
we have a situation where the same view VIEW1 and underlying table, of course, is open in 2 different datasessions, one is the DEFAULT one and another any form datasession. If I update VIEW1 in Form's datasession, save records and close the form, everything is fine, no problem. If I open another form and will try to update the same VIEW1 that was open in DEFAULT datasession, I have an UPDATE conflict. VIEW1 one was requeried after SAVE() in Form's datasession, before attempt to update it in DEFAULT datasession, another words, I was trying to synchronize VIEW1 every time I update it from any place, nothing worked.

It's not that we have a big problem, I can always use VIEW1 opened in DEFAULT datasession to get an information only without updating it. I am just trying to understand why it behaves like that. We have an Optimistic record locking and I am not sure what other information I need to provide. The error occurred while issuing TABLEUPDATE(). My understanding was that as long as TABLEUPDATE() issued and changes were saved to the underlying table in one datasession, the same table in other datasession is updated as well. I understand that I have to REQUERY() the VIEW1 in DEFAULT datasession to refresh it but what can I do to the underlying table to refresh it, I have no idea. I don't want to close it and open it again.
Any ideas on this behavior?
Igor