> Alan,
>
> Thnaks, that sounds like a good idea. One question, what if the
> refresh hits while the "receiver" is adding info of their own?

The refresh doesn't "hit" - the event is "received" - your event response
should do what you want it do. IBO nicely handles Transaction.Refresh(True)
to commit and re-open/return to current record. If you call the same method
as your normal save function, it should be fine.
Alan

>
>
> --- In IBObjects@yahoogroups.com, "Alan McDonald" <alan@m...> wrote:
> > > When user A updates a record, user B needs to see it immediately or at
> > > least within a few seconds. What's the best way to make this happen?
> > >
> >
> > in these cases, I use events - the event receiver must refresh it's
> > transaction to see the committed update from the first user. (of
> course User
> > A's update must be committed)
> > Alan
>