Returns or sets the text of the alternate "busy" message which is displayed in place of the default Component Busy dialog if an ActiveX component rejects an automation request. Not available at design time.
Syntax
object.OLEServerBusyMsgText [= string]
The OLEServerBusyMsgText property syntax has these parts:
Part | Description |
object | An object expression that evaluates to an object in the Applies To list. |
string | A string expression that evaluates to the message text that will be displayed in the alternate message box for the ActiveX component busy condition. |
Remarks
Visual Basic continues to retry an automation request for the number of milliseconds specified by the OLEServerBusyTimeout property. If the ActiveX component has not accepted the request in that interval, Visual Basic displays a default Component Busy dialog box. This dialog box includes text and a Switch To button which are intended for use with visible ActiveX components such as Microsoft Excel. There are situations in which the default dialog box may not meet your needs:
In these situations, the default text and Switch To button are inappropriate and may confuse the user of your program.
The OLEServerBusyMsgText property allows you to replace the default Component Busy dialog box with an alternate message box. Setting OLEServerBusyMsgText to your own message string causes the default Component Busy dialog box to be replaced by a simple message box containing your message text, an OK button, and a Cancel button.
If OLERequestPendingMsgText is equal to an empty string (""), the default Component Busy dialog is displayed.
If the user presses the Cancel button of the default Component Busy dialog box or the alternate message box, the ActiveX error -2147418111 (&H80010001) is raised in the procedure that made the automation request.
Important When you know that an automation request may take more than a few seconds and you are using a hidden or remote ActiveX component, you should set an alternate message. For remote ActiveX components, the alternate message is recommended for all requests. Network traffic may occasionally cause even a very short ActiveX request to take several seconds.