If nobody has a very simple solution, Email me and I'll
explain a bit more involved, but rather generic solution
I used, which may fit your requirements.

-----

paultansit wrote:

>
> I don't know if there is an easy way to deal with this or not.
>
> Most applications will have multiple transactions, and certainly
> different apps don't share the same transactions. A transaction
> only "sees" information that has been updated or added that is
> attached to it's own transaction. When something is changed in
> another app or transaction, what is the best way of updating that
> info to other apps or transactions?
>
> I use a transaction refresh to update, but it seems illogical to have
> to have a user continually press a refresh button. I have also played
> around with IB_Event to notify the app of changes to key records.
>
> How does everyone else deal with this? Is there some generic
> procedures that can be used?
>
> Thanks,
> Paul
>
>
> ___________________________________________________________________________
> 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 !
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/