ODBC - From Scratch - ???
#1
Hi,
Apologies if this is a daft question but I am a total newbie to the world of ODBC.
I have an application that errors out with the message :
A problem was experienced in opening the xxx Application's database.
-2147467259 - Microsoft ODBC Driver Manager. Data source name not found and no default driver specified.
I haven't got a clue what to do now
Please could someone advise me of the next steps to try and resolve this problem?
I open up the ODBC Data Source administrator.
In USER DSN there are no entries relating to
MS Access Database (*.mdb)
In SYSTEM DSN I added MS Access driver v4.00.4403.03 (ODBCJT32.DLL)
Called it XXX with description yyy
Clicked on button to select database.
Selected the database.mdb from network drive and confirmed OK.
In FILE DSN
Empty
Still errors when trying to open the application.
Anyone got any bright ideas ????
Apologies if this is a daft question but I am a total newbie to the world of ODBC.
I have an application that errors out with the message :
A problem was experienced in opening the xxx Application's database.
-2147467259 - Microsoft ODBC Driver Manager. Data source name not found and no default driver specified.
I haven't got a clue what to do now
Please could someone advise me of the next steps to try and resolve this problem?
I open up the ODBC Data Source administrator.
In USER DSN there are no entries relating to
MS Access Database (*.mdb)
In SYSTEM DSN I added MS Access driver v4.00.4403.03 (ODBCJT32.DLL)
Called it XXX with description yyy
Clicked on button to select database.
Selected the database.mdb from network drive and confirmed OK.
In FILE DSN
Empty
Still errors when trying to open the application.
Anyone got any bright ideas ????
#2
ok...
I've had a dig around but most of the errors relating to that number tend to imply that it can't find the database. You can't assume that its using a dsn (user / system / file) I normally dont when I connect.
3 options.
1) Find the database and do a compact / repair on it (this can be done from within access).
2) Reinstall the app.
3) Get the latest MDAC and Jet drivers (on MS site)
more details would help too... what is the app your trying to get to connect and where the db is etc... if that fails try to find the registry entries to see if theres a reference for the app that points to where the db is.... I'll keep an eye on this thread if you have any more problems
I've had a dig around but most of the errors relating to that number tend to imply that it can't find the database. You can't assume that its using a dsn (user / system / file) I normally dont when I connect.
3 options.
1) Find the database and do a compact / repair on it (this can be done from within access).
2) Reinstall the app.
3) Get the latest MDAC and Jet drivers (on MS site)
more details would help too... what is the app your trying to get to connect and where the db is etc... if that fails try to find the registry entries to see if theres a reference for the app that points to where the db is.... I'll keep an eye on this thread if you have any more problems
Thread
Thread Starter
Forum
Replies
Last Post
Scott@ScoobySpares
Full Cars Breaking For Spares
61
11 January 2021 04:08 PM
Scott@ScoobySpares
Full Cars Breaking For Spares
7
14 December 2015 09:16 AM