connection to Access 2007

Sorry, no stars for that reply.

Lots of general information, but here is the crux of the problem:

Your reference from planet-source-code.com gives this

code:

try {

Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");

// set this to a MS Access DB you have on your machine

String filename = "d:/java/mdbTEST.mdb";

String database = "jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};DBQ=";

database+= filename.trim() + ";DriverID=22;READONLY=true}"; // add on to the end

// now we can get the connection from the DriverManager

Connection con = DriverManager.getConnection( database ,"","");

}

Well, that may work with previous versions of Access, but my

question is about Access 2007. Access 2007 does NOT

produce a .mdb file, but rather a .accdb file. So, this code

will obviously fail (and it does!).

Maybe I should give one star, because you pointed to lots of

semi-useful general information, but it does NOT answer the

question!

javaStudenta at 2007-7-10 0:44:58 >

Does it work if you configure the DSN using the ODBC tool from the control panel, then just use the DSN name? I would expect that to work.

Then if it does, get the actual name of the ODBC driver from the ODBC tool. Find the string "Microsoft Access Driver (*.mdb)" in all those examples you were linked to and replace that by the actual name of the driver. I would expect it to look similar to that, but of course be somewhat different.

And I don't know about those other parameters like DBQ and so on. The new driver might have different parameters. Of course that would be in Microsoft documentation somewhere.

You may well be a pioneer. Post answers here if you find them.

DrClapa at 2007-7-10 0:44:59 >

> String database = "jdbc:odbc:Driver={Microsoft Access Driver ...

The problem is in confusing the java driver with the parameters that are provided to the driver.

In the above EVERYTHING after 'odbc:' is data that is provided to the odbc bridge driver (and to the ODBC shell).

And if you need to determine what that information is then often you must figure it out yourself. An excellent way to start doing that is to create a FILE DSN via the odbc applet and then look at the information in that file.

jschella at 2007-7-10 0:44:59 >