jdbc for MS ACCESS

[Gérard DESCHAMPS]

Hello
I try to use the new Features in the JDBC 2.0 api (updateRow , deleteRow
...) with MS ACCESS ==> Unsupported ...
Does the JDBC-ODBC Bridge support these features ?
help ...

[Stefan Zschocke]

Sun' jdbc-driver doesn't support any of the JDBC2.0 features. It just throws
an UnsupporteOperationException from any of the new methods, like those for
scrollable ResultSet. If you need scrollable ResultSets you need another
Jdbc-driver. For example you could try jadoZoom, which is a jdbc-ADO-bridge
and thus well suited for MS Access and and SqlServer.
See http://www.inzoom.com/javaado.html
Stefan

"Gérard DESCHAMPS" <GD...@wanadoo.fr> wrote in message
news:8ckath$chs$1...@wanadoo.fr...

[Gérard DESCHAMPS]

Now , with jadoZoom, the JDBC 2.0 features are recognized but don't modify
my database
My ResultSet is CONCUR_UPDATABLE, but the method updateRow has no effect on
the DataBase
here is the code , where is the problem ?
Thanks

import java.sql.*;
import java.net.URL;
class ExBdd7 {
public static void main(String[] arg) {
new ExBdd7("Essai Bdd");
}
public ExBdd7(String s) {
// accès base de données
String url="jdbc:izmado:test";
try {
Class.forName("com.inzoom.jdbcado.Driver");
Connection contact=DriverManager.getConnection(url,"","");
Statement requete = contact.createStatement();
ResultSet resultat = requete.executeQuery
("SELECT * FROM pers");
resultat.first();
resultat.updateString(1, "JULES");
resultat.updateRow();

resultat.close();
requete.close();
contact.close();
}
catch(SQLException e) {
System.out.println("SQLException"+e.getMessage());
}
catch(ClassNotFoundException e) {
System.out.println("ClassNotFoundException"+e.getMessage());
}

}
}

Stefan Zschocke <s.Zsc...@infozoom.de> a écrit dans le message :
8ckebm$3s3$1...@passat.ndh.net...

[Stefan Zschocke]

Hi,
this is a timing problem, which exists in similar form with the
jdbc-odbc-driver (for insert/update/delete-statements). It has to do with
multithreading but I don't know the exact cause. The fact is, that when the
close returns, the database-closing has not yet finished in the background.
But as the main method finishes, the driver gets unloaded kind of
prematurely without completing. So the changes don't make it to the
database. Just putting System.gc() behind the close statement makes it
working. Another solution is, to work with explicit transactions through
Connection.setAutoCommit(false) and Connection.commit. Still another
solution is, to use the Jet-OleDB-provider, which seems to work better than
the ODBC-driver.
Stefan

"Gérard DESCHAMPS" <GD...@wanadoo.fr> wrote in message

news:8crrnu$ko4$1...@wanadoo.fr...

[Michael Roth]

Unfortunately Sun didn't incorporate the JDBC 2.0 methods into the Jdbc-Odbc bridge. You will have to use a third party driver if you want JDBC 2.0 functionality, or just go back to JDBC 1.0

Gérard DESCHAMPS wrote:

Hello
I try to use the new Features in the JDBC 2.0 api (updateRow , deleteRow
....) with MS ACCESS ==> Unsupported ...
Does the JDBC-ODBC Bridge support these features ?
help ...

[Jason Blight]

Where can I get hold of the Jet-OleDB-provider driver and how do I use it?

Thanks in advance,
Jason

[Stefan Zschocke]

We have developed jadoZoom, a jdbc-ado/oledb bridge. With it you can access
databases through Oledb providers. You need to have OleDB / ADO installed to
use jadoZoom. OleDB and ADO are part of MS MDAC, which is included with
Win2k, Office2k and otherwise can be downloaded without charge from
http://www.microsoft.com/data. There also exists an Oledb-provider for ODBC
so you can substitute Sun's jdbc-odbc bridge with jadoZoom. In contrast to
Sun's bridge, jadoZoom supports most of the jdbc 2.0 specs like scrollable
and updatable cursors. For Access databases it is preferrable to use the
Jet-OleDB-provider instead of the ODBC-provider.
jadoZoom can be downloaded at http://www.infozoom.de/javaado.html
Stefan

"Jason Blight" <jbl...@cableinet.co.uk> wrote in message
news:390732B0...@cableinet.co.uk...