Subject Re: [IBO] Isolating TransActions
Author anthpjc
thanks for replying helen... i'm using ibo 4h
I am not entriely sure why i get this behaviour either, but anyway,
the way i am going through it is as such:
- transA has a transactionsource, trsourceA.
- transB has a transactionsource, trsourceB.

i have a query, qrB that has transB as it's transaction in the
transaction property. when i click to insert i can trace through to
the beforepost of qrB (where if i check the state of transA it is
tsInactive), then on further tracing it goes to the
trsourceAstatuschanged method for some reason where the state of
transA has mysteriously changed to tsActive.

what i am trying to avoid is the trsourceAstatuschanged method code
which is why I have the "B" transactions.

--- In, Helen Borrie <helebor@t...> wrote:
> At 03:57 AM 1/03/2004 +0000, you wrote:
> >Greetings All
> >I have a situation where I have 2 transaction components on a form
> >with different query and datasource components linking to each because
> >I want to keep the queries for each transaction separate.
> >The thing is that when i try to insert on one of the queries the
> >status of the other transaction (the one the query is not using)
> >changes from Inactive to active.
> Can you explain what you mean by "inactive" and "active", with
respect to
> your transactions? What I mean is, what is happening that leads you to
> think that activity in one transaction is affecting the other?
> >This shouldn't be as far as I can see
> >because the query isn't using that transaction, it even makes no
> >difference if I have separate connection components for each of the
> >transactions. why is the separate transaction being affected by things
> >that should be unrelated?
> It doesn't happen. The fact that a certain dataset is "in insert mode"
> doesn't affect any transaction: not even the one that that is
> that dataset.
> We need more information about what you think you are seeing.
> Helen