OFF98: Compile Error Using the Visible Property of UserForms

Last reviewed: February 17, 1998
Article ID: Q181059
The information in this article applies to:
  • Microsoft Word 98 Macintosh Edition
  • Microsoft Excel 98 Macintosh Edition
  • Microsoft PowerPoint 98 Macintosh Edition

SYMPTOMS

When you attempt to set or change the Visible property of a UserForm, you receive the following error message:

   Compile error:

   Wrong number of arguments or invalid property assignment.

CAUSE

This error occurs when you attempt to modify a read-only property. For example, the following sample Microsoft Visual Basic for Applications code generates the error:

   Sub HideForm()
      UserForm1.Visible = False ' Generates a Compile error.
   End Sub

   Sub ShowForm()
      UserForm1.Visible = True  ' Generates a Compile error.
   End Sub

RESOLUTION

Microsoft provides programming examples for illustration only, without warranty either expressed or implied, including, but not limited to, the implied warranties of merchantability and/or fitness for a particular purpose. This article assumes that you are familiar with the programming language being demonstrated and the tools used to create and debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific needs. If you have limited programming experience, you may want to contact the Microsoft fee-based consulting line at (800) 936-5200. For more information about the support options available from Microsoft, please see the following page on the World Wide Web:

   http://www.microsoft.com/support/supportnet/refguide/default.asp

The Visible property is designed to let you check the Visible state of a specific form, but not modify it. To modify the Visible state of a form, use the Hide and Show methods to change the form's Visible property.

NOTE: The following code samples assume your form is named UserForm1. Replace UserForm1 with the name of your form or a reference to your form.

How to Use the Show and Hide Methods

The following sample Visual Basic code hides a UserForm:

   Sub HideForm()
      UserForm1.Hide
   End Sub

The following sample Visual Basic code shows a UserForm:

   Sub ShowForm()
      UserForm1.Show
   End Sub

How to Use the Visible Property

The following sample Visual Basic code checks the Visible property of a form:

   Sub CheckFormState()

      ' Determine whether the form is visible.
      If UserForm1.Visible = True Then
         ' Do something when the form is visible.
      End If

      ' Determine whether the form is hidden.
      If UserForm1.Visible = False Then
          ' Do something when the form is hidden.
      End If

   End Sub

STATUS

This behavior is by design. Microsoft welcomes suggestions or comments about changes in functionality and product design. You are invited to submit suggestions by filling out the form at the following Microsoft Web site:

   http://www.microsoft.com/regwiz/regwiz.asp

REFERENCES

For more information about getting help with Visual Basic for Applications, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q163435
   TITLE     : VBA: Programming Resources for Visual Basic for
               Applications


Additional query words: dialog box dialogs hidden invisible custom
Keywords : kbprg kbdta kbdtacode kbwordvba word97 OffVBA macword98
Version : MACINTOSH:98
Platform : MACINTOSH
Issue type : kbprb


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