> -> IB_connection, IB_Transaction's and all insert, delete or update
> stuff (generally IB_Proc's) are centralized on a unique DataModule.
> So, all insert, delete or update actions are guaranteed to be
> constant through all the application.

I don't think it needs to be quite so completely split. Once
you hit delete on a form it is processed without needing to
go back to the central stuff. Jason would probably say that
any related actions should happen on the server triggers, so
manual intervention in the database also works. That is the
fundamental difference between Client\Server and the older
Flat File single user methods - WHERE the work is done
rather than in which program module.

Also take care when using Windows Timers and other thread
related things. If a clock action is happening in the
background it may be using a different thread, and should
really have it's own connection. It's caught me out so I
have that queries connection actually on the form with the
clock - which seems to be OK.

--
Lester Caine
-----------------------------
L.S.Caine Electronic Services