At 02:32 PM 25-05-02 +0000, you 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?

Other transactions will get the committed changes if their isolation is
tiReadCommitted. The buffers won't receive them until you refresh the
dataset...

>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?

Most certainly - use DMLCaching to have some or all of you datasets
notified when changes occur elsewhere. See the TI sheet on the TechInfo
page and the DML... properties and events of TIB_Dataset in the component help.


regards,
Helen Borrie (TeamIBO Support)

** Please don't email your support questions privately **
Ask on the list and everyone benefits
Don't forget the IB Objects online FAQ - link from any page at
www.ibobjects.com