Hi,

I'm using JDBC-ODBC driver to access MS Access tables.

(Earlier when it was based on MySQL, it was running fine).

While running the program, I get error:

getEmployeeName: Prepare Statement Error ...
java.sql.SQLException: [Microsoft][ODBC Microsoft Access Driver]Optional feature
not implemented
at sun.jdbc.odbc.JdbcOdbc.createSQLException(Unknown Source)
at sun.jdbc.odbc.JdbcOdbc.standardError(Unknown Source)
at sun.jdbc.odbc.JdbcOdbc.SQLBindInParameterBigint(Unknown Source)
at sun.jdbc.odbc.JdbcOdbcPreparedStatement.setLong(Unknown Source)

...

I think the problem lies with setLong().

My code has following:

try {
pstmt.setLong (1, empno);
}

catch (NumberFormatException nex) {
System.out.println("getEmployeeName: Invalid number" + empno);
nex.printStackTrace();
}
catch (SQLException ex1) {
System.out.println("getEmployeeName: Prepare Statement Error ...");
ex1.printStackTrace();
}

......

How to resolve it? Why this code is running fine on MySQL and not in MS Access?

Any help is appreciated.

Thanks in advance.

Rajeev.

 

 

The stack trace suggests that it's because that feature is implemented in your MySQL driver but not in the JDBC-ODBC bridge.

%

 

 

There are also commercial versions of a real JDBC Access driver (rather than the JDBC-ODBC bridge) that might more fully implement the JDBC specification for Access.

- Saish

 

 

I ran into this problem recently, and solved it with setBigDecimal() which does seem to be supported by the JDBC-ODBC bridge.

So my code went from something like this:
pst.setLong( 1, doc.id );

To something like this:
pst.setBigDecimal( 1, BigDecimal.valueOf(doc.id) );

Hope this works for you as well... I know it caused me pain for a while!