PDA

View Full Version : Cant work with MSAccess



ramirobot
01-08-2009, 08:24 AM
i keep getting the "Optional feature not implemented", but its a simple select statement that im trying to do. So i think its some configuration i missed? I can work without a problem with PostgreSQL. here are the details of my xAction:

xAction:
A simple relational query, that outputs the resultset;
jdbc driver: sun.jdbc.odbc.JdbcOdbcDriver
jdbc url: jdbc:odbc:MyDSN
MyDSN is a system dsn that points to c:/MyDB.mdb and uses MicroSoft Access Driver.

I have tried replacing the jdbc driver and/or url string with jdbc:odbc:Driver={MicroSoft Access Driver (*.mdb)};DBQ=c:/MyDB.mdb, but got the same error.
The rt.jar file with the above jdbc driver is in
[pentaho home]\bi-server\jboss\server\default\lib
AND
[pentaho home]\design-studio\plugins\org.pentaho.designstudio.editors.reportwizard_1.7.0.906\lib\jdbc

Im using pentaho 1.7, Eclipse workbench from pentaho to edit xActions, MSAccess 2003. The database is as simple as possible, (One table, 3 colums, the sql was tested within MSAccess and worked fine)

Is there any config specific for working with .mdb files?

bugg_tb
01-08-2009, 08:42 AM
I ran into the same problem with a different person a while ago, basically you're stuffed cause its a jdbc-odbc driver issue from what we discovered. Try using a proper database!

ramirobot
01-08-2009, 09:04 AM
Im working with a legacy system. Eventually we will be moving to PostgreSQL, but for now is MSAccess.

Did you ever made it work with access? i dont understand why its such a hassle, since Foodmart comes in a .mdb file. (wich, btw, i never was able to made it work before moving it to another db)

bugg_tb
01-08-2009, 09:27 AM
Cant remember off hand, it was on google though, in the end the guy used kettle to load the data into mysql before processing it

pstoellberger
01-08-2009, 09:46 AM
I had a similar issue with the JDBC/ODBC bridge and access
solved it like bugg said... moving all the data to CSV or different DB

Taqua
01-08-2009, 09:52 AM
And depending how badly you need a solution, and how much money you are willing to throw at it, you could try one of the many commercial JDBC drivers for MS access. Yes, its not free, but so is MS-Access in the first place.