> A solution would be a driver option (registry key) that says "use
> fbclient.dll directly instead of gds32.dll".

Actually it looks like it may be possible. I've been wading through the ODBC
driver source code and it appears to definitely be possible when using a DSN
to define the connection - there is a "Client" parameter which allows you to
specify the client DLL - C:\Some\Path\fbclient.dll (defaults to gds32.dll in
system32), however it doesn't appear to be possible to specify the client
DLL in the connection string (we don't use DSN's as the database location is
dynamic and it also eases development and installation).

I'm posting a msg to the ODBC driver developer list.

Regards,

Jarrod Hollingworth
Backslash