It sounds to me like you are over complicating things.
Take a look at the IBF_Base form. It has a constructor that allows you to
instantiate a form within a given transaction context or to start one of its
own. See the CreateWithContext constructor. There are lots of comments in
the source code of this base form.

I think it is nice to use more than one transaction to allow the users to
have more than one instance of a form at a time. This means you don't use
datamodules so much. Only for global things. Otherwise, you cannot have
isolated form instances with their own unique transaction contexts.

HTH,
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com

----- Original Message -----
From: "Burak OZLER" <burak.ozler@...>
To: "IB Objects" <IBObjects@yahoogroups.com>
Sent: Friday, August 24, 2001 5:06 AM
Subject: [IBO] Managing Transactions


> Hi All...
>
> I Plan to built a heavy Accounting Program with Interbase and
IBObjects but I have a real Problem Transactions. My Applications works MDI
but a form can be opened once a time. Now I'm using only one Transaction
object. For example The Order or Invoice modules can run at a time each
modules updates deletes fires tons of functions that made DB write and
delete. It's nearly impossible to handle them healty so I have to use
transactions.
>
> I think When a user opens Invoice module and selects "NEW" I have to
get a transaction number and use the number in all functions transactions,
then if user preses "update" for the job I must commit all the changes to
database that have the same transaction number. Or selects Cancel I have to
do a RollBack operation. Think that all items at detail update fires 15
Functions.
>
> I use IB & IBObjects 3.X (trying)
>
> I prefer TDATASET compatible componenets (For Future)
>
> Any reading suggestion.
> Any Idea
>
> will be very valuable for me.
>
>
>
> "Do you think Firebird/Borland Interbase suitable for this kind of
Applications ?"
>
> Thanks
>
> Burak