Hi Grant

The technique I use was picked up at a user group meeting. All lookup
tables are cached in TClientDatasets. When a form needs a copy of a
lookup set it calls a procedure which translates to CloneCursor. The
procedure will first retrieve the lookup set from the server if the
cache is empty i.e. they are populated on demand.

The cache datasets are on a data module which also responds to events.
If it receives an event message that a certain lookup table has been
modifed (fired by insert, update or delete trigger) it flushes the
cache for that table.

It works for me and there is no patent.

Dave

--- In firebird-support@yahoogroups.com, Grant Brown <grant@s...> wrote:
snip
> Now I know that I can resolve this using Firebird "events" but I am not
> sure how to go about this.
>
>
> --
> Regards,
> Grant Brown
>