WD97: Can't Run OCX Control After Converting to Inline Object

Last reviewed: August 27, 1997
Article ID: Q167879
The information in this article applies to:
  • Microsoft Word 97 for Windows

SYMPTOMS

When 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.

CAUSE

When 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.

WORKAROUND

To work around this problem, use these steps:

  1. On the View menu, point to Toolbars, and click Control Toolbox.

  2. Select the control. Click the Properties button on the Control Toolbox.

  3. In the Properties window, change the Name property to its original name.

STATUS

Microsoft 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
Keywords : kbprg kbtool PgmCtrlsStd word8 word97
Version : 97
Platform : WINDOWS
Hardware : x86
Issue type : kbbug


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: August 27, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.