FIX:ClassView Add Function/Variable Fails If Header File Moved

Last reviewed: September 18, 1997
Article ID: Q140270
4.00 4.10 WINDOWS NT kbprg kbbuglist kbfixlist

The information in this article applies to:

  • Microsoft Visual C++, 32-bit Edition, versions 4.0, 4.1

SYMPTOMS

Attempting to add a function or variable to a class by using classview fails and returns this message:

   One or more of the files for <class name> are read-only.

Here <class name> corresponds to the class that is selected.

CAUSE

This is a bug that occurs if the header file for the class has been moved from its original directory.

RESOLUTION

Either choose not to move the header files from their original location, or add member functions and variables manually if you must move the files.

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.

MORE INFORMATION

Moving the wizard-generated header files to another directory results in their appearing as read-only when you attempt to use the classview add function or add variable commands. Even if you add the new directory to the include directory search path and update all dependencies, this problem persists.

The files are not really read-only; they can be opened for editing through all available avenues.


Additional reference words: 4.00 4.10 vcbuglist400 vcfixlist420
KBCategory: kbprg kbbuglist kbfixlist
KBSubcategory: VWBIss
Keywords : VwbIss kbbuglist kbfixlist kbprg
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 18, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.