OFF97: Custom Office Assistant Balloon Cannot Be DismissedLast reviewed: February 27, 1998Article ID: Q164681 |
The information in this article applies to:
SYMPTOMSIn the programs listed at the beginning of this article, if you run a Microsoft Visual Basic for Applications macro that displays a custom Microsoft Office Assistant balloon, the following problems may occur:
CAUSEThese problems may occur when the following conditions are true:
RESOLUTIONTo prevent these problems from occurring, do the following:
Note that you can dismiss the Office Assistant window by clicking the Close button in the upper-right corner of the Office Assistant window while the custom Office Assistant balloon is displayed.
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.
MORE INFORMATIONMicrosoft 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 engineers 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 the Microsoft fee-based consulting line at (800) 936-5200. For more information about the support options available from Microsoft, please see the following page on the World Wide Web:
http://www.microsoft.com/support/supportnet/refguide/default.aspIn the Office 97 programs, you can create and display custom Office Assistant balloons. To do this, use Visual Basic for Applications macros that are similar to the following examples:
' Both macros are contained in the same module, Module1. Sub BalloonTest() Dim Bln As Balloon Set Bln = Assistant.NewBalloon With Bln .Heading = "Heading" .Text = "Some text." .Mode = msoModeModeless ' Make the balloon modeless. .Callback = "Goodbye" ' Run this macro when OK is clicked. .Show ' Display the balloon. End With End Sub Sub Goodbye(Bln As Balloon, iBtn As Long, iPriv As Long) Assistant.Animation = msoAnimationSearching MsgBox "Goodbye!" Bln.Close End SubWhen you run the BalloonTest Sub procedure, the Office Assistant window appears and displays the custom balloon. When you click OK in the balloon, the Goodbye Sub procedure runs and displays a message box. When you dismiss the message box, the Office Assistant balloon disappears. This behavior is correct. If you set the Callback property so that it refers to a misspelled macro name or an incorrect location, the problem described in this article occurs. NOTE: In Microsoft Word 97 and Microsoft PowerPoint 97, if you set the Callback property to refer to a macro that exists in another module, you must specify the module name before the macro name. For example, if you move the macro Goodbye to Module3, change the code to the following:
.Callback = "Module3.Goodbye"If you do not specify the module name, the problem occurs when you display the custom Office Assistant balloon. In Microsoft Excel 97, this is not required if the macro exists in the same workbook.
|
Additional query words: OFF97 XL97 WORD97 PPT97 go away disappear vanish
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |