BUG: 'Out of String Space' Error Returned by the Access Driver

 Last reviewed: September 9, 1996
Article ID: Q130954
The information in this article applies to:
  • Microsoft Open Database Connectivity, version 2.0

BUG# QJet: 2138 (2.00.2317)

SYMPTOMS

Under certain circumstances, when you disconnect and connect to a Microsoft Access database frequently, the 16-bit Access 2.00.2317 driver returns the following error: 

   Out of String Space.

CAUSE

If the following steps are executed, the 16-bit Access driver produces the above error.

  1. Configure two datasources to point to two different Access databases (.MDB files), say DB1 and DB2.

  2. Start the 16-bit ODBC Test.

  3. Make a connection to DB1.

  4. Run a query "select * from <view name>".

  5. Make a connection to DB2.

  6. Run a query "select * from <table name>".

  7. Disconnect from DB1.

  8. Reconnect to DB1.

  9. Run the query same query in step four.

This last step should cause the "Out of String Space" error.

WORKAROUND

If you do not close the connection to DB1, you can execute the query in step four, "select * from <view name>", as many times as you wish. It only happens if you disconnect and reconnect. Also, this problem does not occur with the 32-bit driver.

STATUS

Microsoft has confirmed this to be a problem in the ODBC Access 2.00.2317 driver. There are no plans of fixing this bug in the 16-bit driver.

Additional reference words: 2.00.2317 Access Driver VC++ MFC
KBCategory: kbinterop kbbbug2.00.2317
KBSubcategory:



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: September 9, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.