The information in this article applies to:
SYMPTOMS
Some Visual Basic for Applications procedures that run smoothly in
Microsoft Excel version 5.0 for Windows may run out of stack space when
you run them in Microsoft Excel version 5.0c.
WORKAROUNDTo avoid out of stack space errors, rewrite the procedures such that buttons on custom dialogs do not directly start a secondary procedure; instead, design the macro such that it toggles a Boolean variable (or "flag"). Then, evaluate the flag with an If statement to decide whether or not to call the next procedure. ExampleMicrosoft provides examples of Visual Basic for Applications procedures 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. The Visual Basic procedures in this article are provided 'as is' and Microsoft does not guarantee that they can be used in all situations. While Microsoft Support professionals can help explain the functionality of a particular macro, they will not modify these examples to provide added functionality, nor will they help you construct macros to meet your specific needs. If you have limited programming experience, you may want to consult one of the Microsoft Solution Providers. Solution Providers offer a wide range of fee-based services, including creating custom macros. For more information about Microsoft Solution Providers, call Microsoft Customer Information Service at (800) 426-9400.You can rewrite the procedure in the following way: make sure the button on the dialog previously called Procedure2 can be dismissed and have it call the FlagFlipping procedure instead. To set the button to be dismissable:
Revised Procedures
STATUSMicrosoft has confirmed this to be a problem in Microsoft Excel version 5.0c for Windows. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available. Additional query words: 5.00c
Keywords : xlwin |
Last Reviewed: October 20, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |