ACC: "Invalid String or Buffer Length" Using Raima ODBC Driver

 Last reviewed: May 20, 1997
Article ID: Q116066
The information in this article applies to:
  • Microsoft Access versions 1.1, 2.0, 7.0, 97

SYMPTOMS

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

When you try to import from, export to, or link (attach) a Raima Data Server table using version 1.x of Raima Corporation's ODBC driver, you may receive the following error message : 

   ODBC call failed
After clicking OK, you receive the following message: 

   [Raima ODBC RDS SQL Driver] Invalid string or buffer length [#15016]

CAUSE

Raima Corporation's ODBC driver does not allow spaces in the data source name.

RESOLUTION

Modify the data source name by double-clicking the ODBC icon in Windows Control Panel. In the Data Source box, select the Raima data source, and then click Setup. In the Data Source Name box, modify the data source name so that it contains no spaces and is 32 characters or fewer in length.

MORE INFORMATION

The ODBC driver mentioned in this article is manufactured by Raima Corporation, a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding this product's performance or reliability.

REFERENCES

For more information about the Raima Corporation ODBC driver, check the driver documentation, or contact Raima Corporation.

Keywords : kb3rdparty kberrmsg OdbcOthr
Version : 1.1 2.0 7.0 97
Platform : WINDOWS
Hardware : X86
Issue type : kbprb
Resolution Type : Info_Provided

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.