FIX: CRecordset Members Not in "Add Member Variable" Dialog Box

Last reviewed: December 18, 1997
Article ID: Q167423

The information in this article applies to:

Microsoft Visual C++, 32-bit Editions, version 5.0

SYMPTOMS

This problem only occurs in the German localized version of Visual C++ 5.0. When you have Ctrl+DblClk on a dialog box or "Add Member Variable" in Class Wizard, the member variables in the CRecordset class are not displayed.

CAUSE

The Class Wizard fails to translate the strings.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug has been corrected in Visual Studio 97 Service Pack 1.

For additional information about the Visual Studio 97 Service Pack 1, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q170365
   TITLE     : INFO: Visual Studio 97 Service Packs - What, Where, and Why

MORE INFORMATION

Steps to Reproduce Behavior

Create a new MFC SDI AppWizard project (neu MFC einzeines dokument projekte), and name the project Test.
In MFC AppWizard - step 2 of 6:
a. Click "Datenbankansicht mit Dateiunterstunterstutzung"
```
      (Database view with file support).
```
b. Click Datanquelle... (DataSource...).
c. In the "Datenbankoptionen" (Database Options) dialog box, connect to
```
      an ODBC or DAO database. Select a table from the database.
```
In MFC AppWizard - step 2 of 6 - Click "Fertigstellen" (Finish).
Click the ResourceView for the project and open the dialog resource for IDD_TEST_FORM.
Add an EditBox.
Connect the database fields to the EditBox using one of the following:
a. Press Ctrl+DblClick in the EditBox.
-or-
b. Start ClassWizard (Ctrl+W), click the Member-Variablen (member
```
      variable) tab, select the CTestView class and click "Variable
      hinzufugen...".
```

Either method makes the "Member-variable hinzufugen..." (Add Member Variable) dialog box appear. The "Name der member variable" listbox should show the member variables of the CRecordset derived class CTestSet.

Steps to Work Around this Problem

If you need to connect a field to the EditBox, you have to manually add code to the CTestView::DoDataExchange() function.

For example, if you want to connect to the EditBox to the:

   m_pSet->m_StudentID

variable, add the following line to void:

   void CTestView::DoDataExchange(CDataExchange* pDX)

which is located in the TextView.cpp file as follows:

  DDX_FieldText(pDX, IDC_EDIT1, m_pSet->m_StudentID, m_pSet);

The result should look like the following:

   void CTestView::DoDataExchange(CDataExchange* pDX)
   {
      CRecordView::DoDataExchange(pDX);
      //{{AFX_DATA_MAP(CDbtestView)
      DDX_FieldText(pDX, IDC_EDIT1, m_pSet->m_StudentID, m_pSet);
      //}}AFX_DATA_MAP
   }

Keywords          : MfcDatabase vcbuglist500 WizardIss VS97FixlistSP3 kbtool VS97FixlistSP2 VS97FixlistSP1
Version           : 5.0
Platform          : NT WINDOWS
Issue type        : kbbug
Solution Type     : kbfix kbservicepack

================================================================================

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