Open Database Connectivity Error

[Ladymvb2]

I have a DataBase made in Access 97. I installed Office 2003 & converted by
Database. I get the following error: Data Source Name not Found & no
Default drive specified. My database works fine on my computer at home, but
not at work.

 

[Peter Jamieson]

There have been a lot of changes between Office 97 and 2003 in this area.
Ideally, you would be able to open your existing application and it would
just work, but unfortunately that is not usually possible.

Things to consider and try:
a. Are you trying to connect from a document that was made in Word 97 and
which you are loading in Word 2003? If so, it may be that Word is looking
for an ODBC data source name which does not exist. In that case, your best
bet could be to try (in Word) going through the data source connection
process again, and letting Word use its new default connection mechanism
(OLEDB). SOme Queries will not be displayed as potential data sources, but
tables should be.
b. if you really need to use ODBC, you will need to ensure that ODBC is
installed on your system, that the "ODBC Desktop Database drivers" are also
installed, and that a Data Source Name (DSN) has been set up for Access
databases. Typically, all these things /are/ installed, but for example your
existing Word document may use a DSN that has not been set up on your
system. Probably the easiest route to take is to check Word
Tools|Options|General|"Confirm conversion at open", go through the connectin
process again, and select the ODBC option if available. If it is not
available, that suggests that you do not have an Access ODBC DSN, or ODBC or
the Access/jet driver is not set up.

Peter Jamieson

 

[Ladymvb2]

Okay, but this worked perfectly on my home computer. Same software and
databases. I did the same thing at home as I did at work.

 

[Vanessa]

Ok, but this worked perfectly at home. I have the same software and operating
system, database, etc. I can figure out what's different between at home and
at work.

 

[Ladymvb2]

Ok, but this worked perfectly at home. I have the same software and operating
system, database, etc. I can figure out what's different between at home and
at work.

 

[Ladymvb2]

Ok, but this worked perfectly at home. I have the same software and operating
system, database, etc. I can figure out what's different between at home and
at work.

 

[Peter Jamieson]

If your systems are both identical, then it would indeed be strnage if one
worked and the other did not, which suggests that they are not identical.
For example, they might vary
a. in hardware terms, with possible impact on the specific software modules
loaded
b. in terms of the components loaded when Windows or Office was installed
c. because, e.g. one is an upgrade and the other is a fresh install
d. ...and so on.

I'm just a volunteer and do not work for Microsoft. I can only make a few
suggestions on what might be different, and rely on you to have a look
around and discover, for example, whether ODBC is installed on both systems,
whether you have the same DSN names, whether they are configured the same
way, and so on.

Peter Jamieson