I have solved the problem. What had happened is I had a batch of components
where some of them were wired up to the client via the default session and I
also had an explicit session that other components were hooked together
with.

The problem seems to stem from having two distinct sets of pointers to the
GDS32.DLL exports and using them across a single connection context.

In simpler terms. I probably had a connection acquired through the explicit
session and then some of the queries were acquiring their handles via the
default session.

My solution was to make everything wire up through the explicit session as I
had planned on doing.

Another possible solution could be to make the exported methods global for
my app for all session objects and just let them slam away at them. I have
heard that it should be ok to do this too. That's how it works when you
statically bind to the client...

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