> We know the cause now. Your challenge is to track through the network
> setup and find out why dbhost.mydomain.com is resolving to something
> different in your DSN to what it is resolving to when the thick clients
> connect.
>
> ./hb

If the problem were as you describe, then the ODBC connection would
*never* work, rather than only working when no-one else is logged into
the database. Also, in this case we are using IP addresses rather than
host names, so DNS can't be the cause.

So my original problem still exists. Thanks for trying to help.

Poney Carpenter