PRB: Public Property of a Class Module Can't Be Set to True

Last reviewed: May 22, 1996
Article ID: Q149529
The information in this article applies to:
  • Professional and Enterprise Editions of Microsoft Visual Basic, 16-bit only, for Windows, version 4.0
  • Windows for Workgroups, version 3.11

SYMPTOMS

After installing Visual Basic version 4.0 over a previously installed Visual Basic version 3.0, the Public property of a class module cannot be set to True. When you attempt to set the Public property of a Class module to True, the following error message appears:

   The Public property for Class Class1 cannot be set to True. You do not
   have an appropriate license to use this.

CAUSE

There are two possible causes for this problem:

  • The registry contains some entries for version 3.0 that the version 4.0 setup program did not remove.

    -or-

  • The registry file, Reg.dat, is over 64K. The version 4.0 entries may be ignored.

RESOLUTION

Exit from Windows for Workgroups; from the MS-DOS prompt, find the Reg.dat file and rename the file to Reg.old. Start Windows for Workgroups and reinstall Visual Basic to rebuild the registry. For instructions on how to rebuild the registry and re-registering .reg files, please see the following article(s) in the Microsoft Knowledge Base:

   ARTICLE-ID: Q80393
   TITLE     : How to Rebuild the Default Windows REG.DAT File

   ARTICLE-ID: Q82814
   TITLE     : Re-Registering .REG Files

You may have to install other applications to rebuild their registry settings as well.


Additional reference words: 4.00 vb4win vb416
KBCategory: kbprb
KBSubcategory: SetIns



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