> J> What I would like to be able to do is have a
> J> TIB_Session that has its own client dll so that you can have more than

one

> J> in the app and thus have a Firebird session and an InterBase session in

the

> J> same application. The problem I'm having getting there is I currently

rely

> J> on some global settings for my trace monitor.
>
> I think your only way out is to require IB_Monitor to be hooked to a
> specific IB_Session instance (and having it find the default one like
> the other components do). Not backward compatible, but coherent.

That would defeat the purpose of the monitor.

Why not have a single pass-through for all sessions? Instead of re-routing
DLL calls, let the monitor hook themselves into available sessions?

Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
Server
Upscene Productions
http://www.upscene.com
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com