Microsoft KB Archive/159336

= XL97: Illegal Operation Using Unload with Enter Event =

Article ID: 159336

Article Last Modified on 11/23/2006

-

APPLIES TO


 * Microsoft Excel 97 Standard Edition

-



This article was previously published under Q159336



SYMPTOMS
When you display a UserForm in Microsoft Excel 97, you may receive the following error message:

This program has performed an illegal operation and will be shut down.

If the problem persists, contact the program vendor.

If you click Details, you receive an error message similar to the following:

EXCEL caused an invalid page fault in module FM20.DLL at 0137:60007585.



CAUSE
This problem may occur when all of the following conditions are true:


 * You create a control on the UserForm and attach code to the Enter event. -and-


 * The code that is attached to the Enter event for the control uses the Unload statement. -and-


 * The control has a TabIndex property of 0 (zero).



WORKAROUND
If you must use the Unload statement in the code that is attached to the Enter event for a control, set the TabIndex property to a value other than zero.

To change the TabIndex property for a control, do the following:


 * 1) Select the control on the UserForm.
 * 2) If the Properties window is not visible, click Properties Window on the View menu.
 * 3) In the Properties window, scroll until you see the TabIndex property and type a number other than zero for the property.

NOTE: This method renumbers the TabIndex property for all the controls on the UserForm. Check this property for all the other controls to see whether they are still in the correct order.



STATUS
Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. This problem no longer occurs in Microsoft Excel 2000.



MORE INFORMATION
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 professionals 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 a Microsoft Certified Partner or the Microsoft fee-based consulting line at (800) 936-5200. For more information about Microsoft Certified Partners, please visit the following Microsoft Web site:

https://partner.microsoft.com/global/30000104

For more information about the support options that are available and about how to contact Microsoft, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

Because the Enter event occurs before the focus moves to a particular control, you can use an Enter event procedure to display instructions; for example, you can use a macro or event procedure to display a small form or message box that identifies the type of data the control contains.

The Exit event is similar to the Enter event. However, the order in which these two events are triggered differs. For example, if you select a check box that initiates the Enter event, and you then select another control in the same form, the Exit event is initiated for the check box, and the Enter event occurs for the second control on the form.

To prevent a control from losing focus, set the Cancel argument of the Exit event to a value of True. For example, if you create a command button called CommandButton1 on your UserForm, you can use the following code for the Exit event: Private Sub CommandButton1_Exit (ByVal Cancel As MSForms.ReturnBoolean) Cancel = True End Sub Therefore, if CommandButton1 receives the focus, it does not lose focus when you attach the code to the Exit event for the control.

