Simplest way to get ADO.NET connection string for mdb database

Question

0.00/5 (No votes)

See more:

, +

I'm learning ADO.NET and have been stuck for DAYS trying to get a connection string for a plain, vanilla .mdb database. I've been trying potential connection strings and permutations but NOTHING works; the database connection is never opened.

The ODBC Data Source Administrator lists the driver as: "Driver do Microsoft Access (*.mdb)". Another application can successfully open this database, so I know my system is capable of it.

Can anyone suggest a SIMPLE connection string that will work?

What I have tried:

Tried strings from connectionstrings.com. Tried articles that discussed connection strings.

Posted 25-Aug-18 11:40am

Alan Balkany

Updated 25-Aug-18 12:28pm

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Accepted Answer · 2018-08-25T12:28:00

Solution 1

That should be an older style (Access 2003 and older) database. It normally uses the JET engine, not ACE, though ACE may still be able to open it though.

Provider=Microsoft.Jet.OLEDB.4.0;Data Source=path to database.mdb;

or

Provider=Microsoft.ACE.OLEDB.12.0;Data Source=path to database.mdb;

Of course, you'll need the Access runtime or the appropriate version Office installed to open it, even from your own code, on every machine that's going to use the database.

For JET, it's Access 2003 and below. For ACE, it's any version of Access above 2003.

EDIT:
Oh, and the .MDB file MUST be in a folder the user has read and write permissions to. That does NOT include anything under Program Files.

Posted 25-Aug-18 12:28pm

Dave Kreskowiak

Updated 25-Aug-18 12:30pm

v2

Comments

Alan Balkany 25-Aug-18 18:53pm

Thanks Dave. Tried it and got: "System.Data.Odbc.OdbcException: 'ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified'"

The code:

IDbConnection myConn = new OdbcConnection(GetConnectionString ());
myConn.Open();

The error happens on the Open() call. I'm using your connection string like this:

return @"Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\ps\Data\Database File\xtreme.mdb;";

It happens with both connection strings. What am I doing wrong?

Dave Kreskowiak 25-Aug-18 18:59pm

Ummm...you're using ODBC, not OLEDB. You can't use an OLEDB provider with ODBC.

Change the ODBC stuff to the OLEDB versions:

string connString = GetConnectionString();
OleDbConnection conn = new OleDbConnection(connString);   // DON'T combine statements together. It make debugging code harder.
conn.Open();

Alan Balkany 25-Aug-18 19:05pm

That did it! Thanks Dave! :)