| Subject | Handling "Update conflicts wiht concurrent..." |
|---|---|
| Author | jimmaguire_1949 |
| Post date | 2006-11-10T14:02:57Z |
I use ASTA and IBObjects 4.5 with Firebird 1.5. I have users get
periodic update conflicts that are resolved by refreshing their
form/grid and retrying. I'd like a better way to handle it. The best
I can come up with is to catch the exception and then give the user
the option to either lose their changes or have them automatically
applied by my app which would refresh repost.
Is this a standard/good way to handle locks/update conflicts?
periodic update conflicts that are resolved by refreshing their
form/grid and retrying. I'd like a better way to handle it. The best
I can come up with is to catch the exception and then give the user
the option to either lose their changes or have them automatically
applied by my app which would refresh repost.
Is this a standard/good way to handle locks/update conflicts?