> > In this scenario, ANY update to the table will cause all the clients
> > to requery the Db. This is what I am trying to avoid.
>
> First things first,
>
> The same thing happens when everyone switches on their computers at
> 9am and all connect and get the list within a short interval. Unless
> you are storing data locally at each client and synchronising, you
> are probably doing a brute force query to fill your lookups.
>
> The first thing you need to decide is how quickly the clients react
> to the post event. Do they need to all jump to life the millisecond
> they get the request, or is 30 seconds later acceptable??

the event being received doesn't have to fire a query refresh either. I like
the method where it just changes the color of a record line in a grid or the
background of edit boxes or some other marker. The user then decides if a
refresh is necessary and manually invokes it.

Alan