FIX: Error Occurs When Remove Object That Has Pending CodeLast reviewed: October 29, 1997Article ID: Q134977 |
3.00
WINDOWS
kbprg kbfixlist kbbuglist
The information in this article applies to:
SYMPTOMSWhen a new form or a form that has been recently modified is instantiated for the first time by using the DO FORM <formname> command or by any other means, the user sees an error message and Visual FoxPro closes.
CAUSEIn one of the methods of one (or more) of the objects, the developer has placed at least one command in the code call stack. (The code call stack is a list of pointers to Visual FoxPro commands that will run when a specified event takes place.) The code placed in the call stack is triggered by a specific event. In this case, the specific event takes place during the form load procedure. That triggered code, or other code in a method of one of the other objects on the form, removes the object and its methods from the form. Therefore, when the pointer in the call stack triggers the code, the problem occurs because the owning object, along with the code, has been removed.
WORKAROUNDThere may be times when the developer needs to have an object rendered invisible to the user. Rather than issuing a REMOVEOBJECT, the developer can set the object's visible property to false (.F.).
STATUSMicrosoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. This problem was corrected in Visual FoxPro 3.0b for Windows.
MORE INFORMATION
Steps to Reproduce Problem
|
Additional reference words: 3.00 VFoxWin fixlist3.00b buglist3.00
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |