Question ODBC Microsoft Access Driver Optional feature not implemented

diegazo

New member
Local time
Yesterday, 18:12
Joined
May 17, 2010
Messages
2
Hi all,

I'm new in this forum so please point me to the correct place where to post my question if this is not the correct one.

I'm currently trying to connect from an SAP java component to an 2003 MS access db. In the above SAP component we need to define what its known as a mode to allow updates, deletes and inserts actions to the an specific db table.

However, the connection could not be established since the following error message is obtained: ): ERROR: Attempt to access JDBC connection failed with "[Microsoft][ODBC Microsoft Access Driver]Optional feature not implemented"

The parameters being used are as follows:

JDBC Driver: sun.jdbc.odbc.JdbcOdbcDriver
Connection: jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};DBQ=C:/My.mdb

Is there any available workaround besides of using a non free third party JDBC-ODBC bridge? Is this a DB limitation or a JDBC driver limitation?

BTW, my platform is Windows Vista Home Basic. I’ve also tried on Windows 2003 Server SP2 but with the same result.

Could you please help me in determine the cause of this issue?

Thanks and best regards
 
Last edited by a moderator:
You shouldn't need to be specifying the Java driver, but only the Access driver from Java.

See ConnectionStrings.com for more about the Access driver options. You can try using OLEDB instead of ODBC but there is also an ODBC connection to Access shown.
 
Hi Bob,

Thanks for your reply, however is required for my configuration to indicate the jdbc driver. The error I'm getting is because of some missing DB features?

Thanks in advanced.

Regards
 
it might be a non-complete access installation

there are a lot of filters and things that dont get automatically added - try reinstalling access to "run everything from my computer."

having said that, i dont thnik i've ever seen a JDBC driver. Is this a "Sun" special of some sort.
 
And I've NEVER seen something where you specify TWO ODBC drivers. ONE Driver translates between the two sources. I can't imagine why you would need to specify TWO.
 

Users who are viewing this thread

Back
Top Bottom