I use the same setup for quite some time now with version 3.xx of IBObjects
and never run into that problem, using cached and immediate updates on
Asta site of things. I don't dare to try it with IBObjects 4.xx or later,
believing leave good enough alone.

----- Original Message -----
From: "jimmaguire_1949" <jimmaguire@...>
To: <IBObjects@yahoogroups.com>
Sent: Tuesday, November 07, 2006 7:49 PM
Subject: [IBO] Handling "Update conflicts wiht concurrent..."


>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?
>
>
>
>
>
> ___________________________________________________________________________
> IB Objects - direct, complete, custom connectivity to Firebird or
> InterBase
> without the need for BDE, ODBC or any other layer.
> ___________________________________________________________________________
> http://www.ibobjects.com - your IBO community resource for Tech Info
> papers,
> keyword-searchable FAQ, community code contributions and more !
> Yahoo! Groups Links
>
>
>
>
>