>
> Actually, Michael, Svein's question is very astute. If you have an
> IB_Transaction (or an IBOTransaction, for that matter) then you

have

> (potentially) two transactions. One is that one, the other is the
> <Default> transaction to which your statement will be assigned if

you

> forget to select the one you added.
>
> Dropping a transaction object onto your datamodule doesn't make it

the

> default transaction. You can, however, make it so, by picking that
> transaction as the DefaultTransaction property of your

IB_Connection or

> IBODatabase.
>
> I consider it is good practice to *always* put down your own

transaction

> object(s) and never to make any assumptions about the <Default>

transaction

> By that, I am not saying there is anything *wrong* about <Default>
> transaction, just that it is sometimes easy to overlook the obvious

if you

> don't pay explicit attention to it.

I actually did that friday and saturday !

But I'll just check again to see, that I actually didn't do anything
wrong.

But as explained earlier I have 7 datamodels.
6 of those uses they own transaction comp.
And those 6 are not being called, referenced or anything, so they are
out of the picture.

But the last datamodel uses default transaction from the database
connection.
I actually changed that friday, but as said, I'll check again.

I'll return with an answer shortly.....


Thanks anyway.

Michael

>
> Helen
>
>
>
> >Regards
> >Michael
> >
> >
> >
> >
> >
>
>_____________________________________________________________________

______

> >IB Objects - direct, complete, custom connectivity to Firebird or

InterBase

> > without the need for BDE, ODBC or any other layer.
>
>_____________________________________________________________________

______

> >http://www.ibobjects.com - your IBO community resource for Tech

Info papers,

> >keyword-searchable FAQ, community code contributions and more !
> >Yahoo! Groups Links
> >
> >
> >
> >