Geoff,

G> I have never liked trying to use the order of the uses items.
G> It is so easily broken and far from explicit because most of
G> the time the order can be ignored.

well it is explicit, and it cannot be ignored. Many tools that need to
be loaded before everything else in an application require to be put
at the beginning of the uses clause. It's not really trying to use the
order, just the first item. WRT to the "never liked" part, I'm not
going to argue of course. :-)

G> Its funny actually, I was going to "pick on you" for trying to
G> assign a value to a constant (IB_GDS32) but checked first and
G> discovered it is a "var" - not what I expected in IB_CONSTANTS,
G> I did not even think about trying to assign to it. Oh how easy
G> it is to miss the obvious!

that's what people have been doing for years.

G> I do like my solution better. It is much more
G> flexible about where and how you get library name. You can
G> actually start an application and open a form with lots of IBO
G> stuff on it and then read your registry settings to get all
G> the various bits and pieces you want and then finally assign
G> the library name before starting a connection. Even better
G> you can, with care, close your connection, unload your library
G> and then start a new connection with a different library - not
G> something I need right now but could be useful down the track.

Agreed. You might know it or not (probably not) but I once did quite a
bit of work to allow IBO to load multiple client libraries at once,
one for each session component. It never made it into IBO (probably
because it had a glitch with the monitoring stuff, that required an
- albeit small - performance hit to be solved) and I am no longer
interested in that functionality. I'm all for flexibility; I just
thought you might be interested in some details you were apparently
missing.

Ciao
--
Nando Dessena
http://www.flamerobin.org