Really noone who can help? I coundn't find a working solution yet. Exporting tables directly from MS Access DOES export those long binaries. But doing it from ADO-code fails. In the sql trace log I saw that the binaries are splitted in chunks of approx. 4kb. I dont't know how to do this from code. Further I found the following statement in the SQL Reference:
"The update statement can only be used to assign a value to columns with the data type LONG if it contains a parameter or NULL specification. The assignment of values to LONG columns is therefore only possible with some database tools." What does that mean? That it can only be done via ODBC-API ? What are theese mysterious "some database tools"? Thx for any hints! Sascha PS: I'm working on W2000 and SAPDB 7.3, ODBC 7.3 > 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? _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
