Hi Jason!

>A thought that just came to me is, wouldn't it be cool if I made a call to a
>stored procedure (and if it doesn't exist just ignore things) that allows
>someone to return configuration settings for a connection ...

IMHO every application programmer has his own strategies where to
store the presets, especially frontend specific configurations
(registry or local / network file, a dedicated db table or even a sp,
with a validity of the data for the whole system or a single computer
/ user etc.). All of these methods are already sufficiently supported
and can be realized with a handful lines of code. So, I beg you, use
your valuable time for tasks of greater importance.

But it would be nice, if a change of the property in question not only
takes effect before establishing a connecting to the database, so that
the desired settings can be retrieved from this location without the
need of a reconnection afterwards.

>... so that people wouldn't even have to recompile their applications.

Why recompile? Existing apps aren't broken by this client side
modification. And with a defensive default setting after an IBO update
nothing has to be done by those who accept the actual behaviour.

BTW: This is how JayBird says NO to strings of exceptional length:
'SQL Error: Creation of a Prescription: Data truncation'

Regards

Christian