BUG: Wizards May Display Invalid Table Names for CRecordset

 Last reviewed: January 9, 1997
Article ID: Q155370
The information in this article applies to:
  • The AppWizard, included with: Microsoft Visual C++, 32-bit Edition, version 4.2

SYMPTOMS

When selecting ODBC database support in the AppWizard or ClassWizard, the list of table names contains entries that are invalid.

CAUSE

AppWizard and ClassWizard incorrectly handle table names.

RESOLUTION

A possible workaround to this problem is to create your recordsets using an alternate datasource, such as an Access MDB file, which contains the same table and column definitions as your original datasource. Then change your code to access the correct datasource instead.

If your table names contain 30 characters or more, it may help to rename them to have fewer than 30 characters.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.

KBCategory: kbusage kbtool kbbuglist
KBSubcategory: WizardIss
Additional reference words: 4.20 kbdsd SQL Server vcbuglist420




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