ODBC, Excel, SQL Server

I have a user accessing SQL Server 2000 data through Excel
and MSQuery...we have used ODBC DSN with no probs. It is
only this user with an issue, so very specific to their
setup somehow.
Example databases called A and B.
User had ODBC DSN set up to default database A.
We want it to be B.
Edited DSN to have default database of B.
No prob. Saved, verified, successful. Just like in past.
HOWEVER, when creating a NEW Excel spreadsheet and NEW DB
Query using this DSN, it STILL points to database A for
some reason. There are no other DSNs with this name
(system, file, or user).
Any idea why it is pointing to the old db, and WHERE it is
getting this from? I have tried removing the DSN and
recreating it. I have tried using other people's logins
instead of his. This works fine on any other computer we
try it on.
Perplexed,
SharonI think this might be caused by using an Excel data source that points to
the old ODBC DSN. Excel builds its own wrapper for ODBC data sources and
typically stores them as .odc files. These are separate entries from the
ODBC data source that you build using the ODBC Administrator. Try opening
Excel, using the Data | Import External Data | Import Data option to display
the Select Data Source dialog. Then delete the old data source by right
clicking on it and selecting Delete from the pop-up menu. Once the old Excel
data source file is deleted build a new one by clicking the New Source
button and following the wizard dialogs.
Mike O.
"Sharon" <beall2@.llnl.gov> wrote in message
news:12e3201c411fc$714a9300$a301280a@.phx
.gbl...
> I have a user accessing SQL Server 2000 data through Excel
> and MSQuery...we have used ODBC DSN with no probs. It is
> only this user with an issue, so very specific to their
> setup somehow.
> Example databases called A and B.
> User had ODBC DSN set up to default database A.
> We want it to be B.
> Edited DSN to have default database of B.
> No prob. Saved, verified, successful. Just like in past.
> HOWEVER, when creating a NEW Excel spreadsheet and NEW DB
> Query using this DSN, it STILL points to database A for
> some reason. There are no other DSNs with this name
> (system, file, or user).
> Any idea why it is pointing to the old db, and WHERE it is
> getting this from? I have tried removing the DSN and
> recreating it. I have tried using other people's logins
> instead of his. This works fine on any other computer we
> try it on.
> Perplexed,
> Sharon
>