We have a 3rd party app that uses ODBC to connect to the server. It offers a
DSN login screen, we select a database name (A), then we're told that it
cannot open database B.
There is no database B on the server. What's happening is this: B used to
exist, the login's default database was set to B, then B was deleted.
syslogins still shows B as the default database.
When we contacted the company, asking them why the connection would not be
using the selected A database, but the default database, they said their
product is not at fault it must be "some setting" on SQL Server. This
doesn't make any sense to me, however. Can anyone shed some light on this?
SQL 6.5 - ODBC 3.x