Sorry to keep adding, but while I'm waiting for help, I'm trying to resolve
the problem myself.

It appears that the problem will still pop up even with closing the
connections in the main thread prior to executing the thread, but it takes
running the thread a few times in a row to do so.

Again, any help is greatly appreciated!



Bill

-----Original Message-----
From: Bill Morrison [mailto:bmorrison@...]
Sent: Friday, August 03, 2001 10:14 AM
To: 'IBObjects@yahoogroups.com'
Subject: RE: [IBO] Unexplained behavior from DefaultSession - Addendum


One additional piece of information is that this error does not occur if all
the main form TIB_Connections are closed prior to creating and executing the
thread.


Bill M

-----Original Message-----
From: Bill Morrison [mailto:bmorrison@...]
Sent: Friday, August 03, 2001 10:04 AM
To: 'IBObjects@yahoogroups.com'
Subject: [IBO] Unexplained behavior from DefaultSession


Greetings All!

IBO 3.5.Ag, IB 5.6

I'm working on a multi-threaded application with the following
characteristics:

Main form maintains 1 TIB_Connection, but has two others it occasionally
uses.

Main form can create a thread, which creates it's own two TIB_Connections
and runs queries from them.

Each TIB_Connection has it's own TIB_Transaction, with explicit code doing
commits/etc.

The problem occurs when I create the thread, one of the thread databases is
over a slow connection (dialup), and I am retrieving blobs from that
database.

Intermittently the following error occurs between image reads :

ISC Error Code : 335544332
invalid transaction handle (expecting explicit transaction start)

The callstack looks like this:

TIB_SessionBase.HandleException
TIB_Transaction.API_Commit <--Self.Name = DefaultSession
TIB_Transaction.CheckOAT
TIB_Transaction.DoTimer(false)


Now, I have tried everything I could think of, including adding TIB_Sessions
and the like, but this error keeps popping up. Any ideas on how I can fix it
would be greatly appreciated.


Thanks in advance!


Bill Morrison




Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/