Problem to connect to mdb using java on solaris 10

Question

hello I'm trying to connect to my mdb using the code below
String database = "/export/home/test.mdb"; String url = "jdbc:odbc:DRIVER={Microsoft Access Driver(*.mdb)};DBQ="+ database+ ";DriverID=22;READONLY=false"; try           { Class.forName("sun.jdbc.odbc.JdbcOdbcDriver"); conn = DriverManager.getConnection(url);           }           catch (Exception e)           { System.out.println(e.getMessage());           }           finally           {               if (conn != null)               {                   try                   {                       conn.close ();                   }                   catch (Exception e) { /* ignore close errors */ }               }           }
the javac returns no errors, but when I'm trying to run the program "null" is printed ( I think that is the e.getMessage). I supose that conn is null and I don't know why. I'm sure that test.mdb exists and it is located to /export/home. I think the problem is that I haven't install an odbc driver on solaris for mdb I don't know where to find it (if anyone can give me a link !!!), but I'm not so sure if this is the problem.
help me please
thanks in advance.

Answer 1

pkwooster wrote:
Joe, I know that you are a skeptic, and need proof for everything said. I heard about the demise of Access, or more correctly the database most frequently associated with the Access front end, JET, several years ago from a Microsoft employee. Yet it is still here.
There is plenty of documentation online about this. Here's just one example: http://www.answers.com/topic/microsoft-jet-database-engine?cat=technology. MS themselves are rather less clear.
That link would suggest that MS Access 2007 is not in fact SQL Server.
MS has been trying for at least 5 years to wean its users off Access-JET and onto one flavour or another of SQL/Server. I'm a Microsoft Partner and see their marketing on a regular basis. Access is rarely mentioned and SQL Server is a hot topic. Note that most MS/Office applications, such as Outlook now use SQL/Server.Ok.
However marketing is different than technology. In terms of that I can only note that I don't see Bob on my desktop.
And Office 2007 is still using Access (which apparently is not SQL Server according to what you posted.)
Conversely, for example, Microsoft has specifically announced that FoxPro will no longer be supported.
Thus I am still looking for something that would suggest that either it is SQL Server right now (2007) or that it shortly will be - like perhaps the beta for the next version is.
And I can only note that some of the stuff that Access does would be difficult to seamlessly do via SQL Server. The article that you posted suggests that upgrades from MS Access exist but that those can lose functionality that will require manual work to replace. Thus if MS did decide to replace Access in Office with SQL Server they would need to come up with a solution for that or risk people not upgrading.
I am not claiming that this can't happen but rather that I question whether it is relevant to suggest that it anything of concern in the near future (especially for an app that is targeting it anyways.)