FIX: ClassWizard Quits If Class Twice Derived from CRecord

 Last reviewed: September 19, 1997
Article ID: Q147735
4.00 4.10 WINDOWS NT kbusage kbbuglist kbfixlist

The information in this article applies to:

  • The Microsoft Foundation Classes (MFC) included with: Microsoft Visual C++, 32-bit Edition, versions 4.0, 4.1

SYMPTOMS

Under circumstances similar to the following, ClassWizard may cause an access violation:

  • You derive a class, CMyRecordset1, from CRecordset using ClassWizard.
  • You derive another class, CMyRecordset2, from CRecordset using ClassWizard.
  • You replace all occurrences of CRecordset in the .cpp and .h files for CMyRecordset2 with CMyRecordset1

The result is that CRecordset2 will be derived from CRecordset1. When ClassWizard is invoked to view CMyRecordset2, an access violation may occur. This problem has been verified with both CRecordset and CDaoRecordset.

RESOLUTION

Leave occurrences of CRecordset in the ClassWizard comments. Particularly, don't change: 

   //{{AFX_FIELD(CRecordset2, CRecordset)
to: 

   //{{AFX_FIELD(CRecordset2, CRecordset1)

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This problem was corrected in Visual C++, 32-bit Edition, version 4.2.

Additional reference words: 4.00 4.10 vcbuglist400 vcfixlist420
KBCategory: kbusage kbbuglist kbfixlist
KBSubcategory: WizardIss
Keywords : WizardIss kbbuglist kbfixlist kbusage
Technology : kbMfc
Version : 4.00 4.10
Platform : NT WINDOWS
Solution Type : kbfix

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