Tim

I have been playing with restricted transactions and it helps a lot to solve
freeze problems when the application is being used by many users (many
modules). But one problem with this way of programming is too easy to forgot
including one or more tables in a list of tables to be controled by a
transaction.

To solve this problem, because I have THProQuery and THProTable inherited
from respective components of DBISAM, I created a little consistence in
Delete, Post and ExecSql of this components and when one of this methods is
used from a table and a restricted transaction is in use and this table was
not inside the scope of transaction, it fires an exception.

You can still control this behavior using a property at engine level or even
in dataset level.

With my components it is too easy to control and works very well (preventing
a lot of bugs).

This is my suggestion.

Eduardo

Eduardo,

<< With my components it is too easy to control and works very well
(preventing a lot of bugs). >>

Good idea.  I'll put it on the list.

--
Tim Young
Elevate Software
www.elevatesoft.com