WD97: Can't Run OCX Control After Converting to Inline ObjectLast reviewed: August 27, 1997Article ID: Q167879 |
The information in this article applies to:
SYMPTOMSWhen you convert an OCX control (for example, a command button), which has Visual Basic for Applications code attached to the control event procedure, from a floating object to an inline object, you cannot run, edit, or view the code. NOTE: To convert an object from a floating object to an inline object, select the object, on the Edit menu, point to "<Object Type> Object," click Convert, and then click to clear or select the Float Over Text check box.
CAUSEWhen you convert the OCX control from a floating object to an inline object, the Name property of the OCX control changes. As a result, the Visual Basic for Applications code is no longer associated with the event procedure.
WORKAROUNDTo work around this problem, use these steps:
STATUSMicrosoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
|
Additional query words: 8.0 8.0 vb vbe vba
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |