Error 'Optional Feature not implemented' when connecting to Microsoft Access in LANSA Composer

Date: 21 April 2009
Product/Release: LANSA Composer 2.0
Abstract: [Microsoft][ODBC Microsoft Access Driver] Optional Feature not implemented : Error when running Transformation Map
Submitted By: LANSA Technical Support


The instruction in Composer 2.0 Guide – Tutorial LIC003, Step 7 concerning creating the database configuration for the MS Access database on the Windows server is incorrect. The instruction is to set the 'Transaction Isolation' in the database configuration to Read uncommitted.

When using LANSA Composer server running on Windows using the supplied MS Access tutorial database, please note the following:

If your Database Configuration has the 'Transaction Isolation' set to 'Read Uncommitted' (ISOLATION(*READUNCOMMITTED)) then you might get the following error when connecting to the database

stack trace: 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.SQLSetConnectOption(Unknown Source)
at sun.jdbc.odbc.JdbcOdbcConnection.setTransactionIsolation(Unknown Source)
at com.lansa.jsm.service.p.a(Unknown Source)
at com.lansa.jsm.service.p.<init>(Unknown Source)
at com.lansa.jsm.service.MapForceService.for(Unknown Source)
at com.lansa.jsm.service.MapForceService.if(Unknown Source)
at com.lansa.jsm.service.MapForceService.command(Unknown Source)
at Source)
at com.lansa.jsm.b.a(Unknown Source)
at Source)

Command : ERROR : "[Microsoft][ODBC Microsoft Access Driver] Optional Feature not implemented"


For the MS Access database, the 'Transaction Isolation' value must be set to 'None' because the MS Access database/driver does not support this functionality. If set to 'Read uncommitted', a run-time error will result to the effect that an "Optional feature is not implemented".