ID: Q182594
The information in this article applies to:
When you run a macro in a Visual Basic for Applications project, the value for a global variable is reset to nothing (zero).
This problem occurs when the following conditions are true:
-and-
To resolve this problem and ensure that all global variables retain their scope, close all UserForm windows before running a macro in a Visual Basic project.
Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article.
The scope of a variable is determined by the way you declare the variable. In Visual Basic for Applications, you can use three kinds of variables: procedure, module, and public. To declare a global variable, use the Public, Dim, or Private keyword in the Declaration section of the module or procedure.
For additional information about the scope and lifetime of variables in Visual Basic for Applications, please see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q141693
TITLE : VBA: Scope of Variables in Visual Basic for Applications
ARTICLE-ID: Q161536
TITLE : How to Temporarily Hide a UserForm
For more information about Scope of a variable, click the Office Assistant, type "Scope", click Search, and then click to view "Understanding Scope and Visibility."
NOTE: If the Assistant is hidden, click the Office Assistant button on the Standard toolbar. If Microsoft Help is not installed on your computer, please see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q179216
TITLE : OFF98: How to Use the Microsoft Office Installer Program
Keywords : kbprg kbdta OffVBA
Version : MACINTOSH:98
Platform : MACINTOSH
Issue type : kbbug
Solution Type : kbpendingLast Reviewed: June 11, 1998