Java on Linux with .MDB file

Question

Hi,
I have created a small java project (experementing actually) to connect to my database .mdb in windows. it works find in my windows environment (Vista + Java + .mdb). I created a .jar file and try to execute it in the Linux (obundu) the program opens but it does not connect to the database instead it throws an error (null),
I am using the DNSless connection. I have attached the code for checking
   Connection getConnection() throws Exception {
    try{
        String dir=System.getProperty("user.dir")+"/db/Client.mdb";
    System.out.println("1");
         Driver d = (Driver)Class.forName("sun.jdbc.odbc.JdbcOdbcDriver").newInstance();
    System.out.println("2");
         Connection c=DriverManager.getConnection("jdbc:odbc:Driver={Microsoft Access Driver(*.mdb)};DBQ="+dir, "admin", "pass");
    System.out.println("3");
    return c;
    catch (exception e){
       System.out.println(e.getMessage());
        System.out.println("4");
    }When I run this code in linux (I have included some print statements for debugging purpose) it print 1,2,null,4
but with windows 1,2,3 (which has opened the connection)
could anyone help me with this connection. I have even installed jdk 6 with netbeans in my linux pc to re-compile in linux itself to check. I still get the same error. the programme not connecting to the database
Thanks

Answer 1

jwenting wrote:
jschell wrote:
jwenting wrote:
there is no ODBC on Linux, hence no bridge driver.ODBC exists on unix.not as standard. Not sure what you mean. It available for most flavors of unix including linux, solaris, OSX, HPUX and AIX.
How more 'standard' does it need to be?
Even if it is installed on OPs machine, it's a fair bet that OP doesn't have a valid DSN set up and doesn't know how to configure one.Could be. But the fact that they are using MS Access means that that point is meaningless.
>
Bridge driver exists on linux.
never seen it, but then I've never looked for it because it's rubbish.That for course doesn't mean it doesn't exist. It exists in all of the Sun VM releases.
>>>
You never use the bridge driver. Not only is it complete rubbish, but it is also a class from the sun.* packages and none of those should ever be used directly.The notation of the bridge driver being a sun.* package is not relevant. One must use the bridge driver or another ODBC driver when using an ODBC only source.
One should never use the bridge driver. It's rubbish. See the documentation for the driver.The driver was donated to Sun by a company that was at the time and still does sell java ODBC drivers. The documentation was probably worded that way specifically to steer people to the commercial drivers.
I have never seen a single problem with the driver itself. The driver up until recently I believe (rather strongly since I have seen bug reports on it for interim releases) was used for unit testing all of the JDBC functonality for the Sun VM releases.
When it was released it was basically the only driver and certainly the only free one. I am rather certain that many projects were successful with it. It was certainly used successfully by me on a large system.
If you insist on using ODBC through Java, get another driver.
mdb file is a MS Access file.I know that... It's however completely irrelevant here, as all that counts is that there's a bad driver being used (and almost certainly incorrectly too).You have a completely different view of the problem domain than I do then. I provided all of the possible solutions for the problem domain that I saw.