Access 2010 Adapter Limitations

Supported Types

This adapter supports types as follows.

Data type	Field size	Type name	Support	Remarks
Text type		VARCHAR type	Limited
Memo type		LONGCHAR type	Limited
Numeric type	BYTE type	BYTE type	Limited
	Integer	SMALLINT type	Yes
	Long integer	INTEGER type	Yes
	Single precision floating type	REAL type	Yes
	Double data type	DOUBLE type	Yes
	Replication ID type	GUID type	Limited
	Decimal type	DECIMAL type	Yes
Date/time type		DATETIME type	Yes
Currency type		CURRENCY type	Yes
Auto number type	LONG INTEGER type	COUNTER type	Yes
Auto number type	Replication ID type	GUID type	Limited
Yes/No type		BIT type	Yes
OLE object type		LONGBINARY type	Yes
Hyper link type		LONGCHAR type	Yes
Attached file		LONGCHAR type	Limited	Retrieve attached file name.

Tables related to the [Table relation information] in the table browser are not displayed.

Replication ID type
- Replication ID type data can not be read.
Text type
- Retrieved as Byte length and not String length, when connecting via JDBC Proxy Server.
Memo type
- If double-byte letters exist in a certain location, data will not be retrieved properly.
  For more details on problems and preventive methods, see "How to obtain memo type data from a mdb file using ODBC API" in the Microsoft Support Team Blog (http://blogs.msdn.com/b/jpsql/archive/2011/09/26/odbc-api-mdb.aspx).
Attachment
- If attached file does not exist, empty character will be retrieved.
Retrieving numeric type data from the table that fits the conditions below, can means that the appropriate data may not be retrieved yet.
- The first column of the table is text type, and the field size is "9".
- Simultaneously retrieves both the data of text type column and numeric type column, of which the field size is "9".
Upper/lower case is not distinguished in table name even when table name is enclosed in quotation marks.

Replication ID type
- Replication ID type data can not be read.
Text type
- Retrieved as Byte length and not String length, when connecting via JDBC Proxy Server.
Memo type
- If double-byte letters exist in a certain location, data will not be retrieved properly.
  For more details on problems and preventive methods, see "How to obtain memo type data from a mdb file using ODBC API" in the Microsoft Support Team Blog (http://blogs.msdn.com/b/jpsql/archive/2011/09/26/odbc-api-mdb.aspx).
Attachment
- If attached file does not exist, empty character will be retrieved.
Retrieving numeric type data from the table that fits the conditions below, can means that the appropriate data may not be retrieved yet.
- The first column of the table is text type, and the field size is "9".
- Simultaneously retrieves both the data of text type column and numeric type column, of which the field size is "9".
Can not execute SQL statements with Nz function.

BYTE
- Batch update is not supported when the type of the column to write contains BYTE type.
Attachment
- Can not be written
Upper/lower case is not distinguished in table name even when table name is enclosed in quotation marks.

BYTE
- Batch update is not supported when the type of the column to write contains BYTE type.
Attachment
- Can not be written.
Can not execute SQL statements with Nz function.

Exception Name		Cause	Actions
java.sql.SQLException	[Microsoft] [ODBC Microsoft Access Driver] Table '<table name>' could not be locked because it is currently used by another user or process.	The target mdb file is in use for other process.	Please check the mdb file in Access specified in the ODBC data source.
	[Microsoft] [ODBC Microsoft Access Driver] File'(unknown)' was not found.	A mdb file cannot be found.	Please check the mdb file in Access specified in the ODBC data source.
	[Microsoft] [ODBC Driver Manager] data source name and the specified default driver was not found.	ODBC data source could not be found.	Ensure the [ODBC data source name] specified is correct.
	[Microsoft] [ODBC Microsoft Access Driver] input table or query '<table name>' was not found.	A table does not exist or the table name is inaccurate.	Please confirm if the table specified in [Table name] exists and if the name is accurate.