ACC2: 32K BLOB Limit Using ORACLE 6.0 ODBC Driver

Last reviewed: May 20, 1997
Article ID: Q121675

The information in this article applies to:

Microsoft Access version 2.0

Advanced: Requires expert coding, interoperability, and multiuser skills.

The ORACLE ODBC driver specification states:

   The limit in ORACLE 7 for long values (CHAR and BINARY) is 2 GB.
   The limit in ORACLE 6 is 64K. The limit imposed by OCI is 32K, so
   this becomes the practical limit for long values of any kind.

Because the current ORACLE ODBC driver (version 6.0) uses OCI, the limit for any long value, such as a binary large object (BLOB), is 32K.

You will encounter this ORACLE ODBC driver limitation whenever you try to save graphical information, such as a bitmap, to an attached ORACLE database using Microsoft Access.

ORACLE is manufactured by Oracle Corporation, a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding this product's performance or reliability.

Additional query words: attaching
Keywords : kb3rdparty OdbcOracl
Version : 2.0
Platform : WINDOWS
Hardware : X86
Issue type : kbinfo

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 20, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.