Actually I'm trying to write a converter for MS Access databases. Export of tables, relations and constraints via OLEDB succeeded with one exception: OLE type columns (long binaries, created as LONG BYTE) fail to export their contents without any error replied from the ODBC driver. While debugging everything seems to work, but in the exported table the records containing NOT NULL values in theese fields are missing! I'd expect that an error should occur but it doesn't. Exporting records with an INSERT VALUES statement and hex strings (e.g. X'FFFF...') would be a workaround but is rejected for large binaries (SQL statement too long). How does the ODBC driver handle BLOBS; have the binaries to be splitted and transmitted in subsequent statements?
Thanx, Sascha _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
