Release 10.1A: OpenEdge Deployment:
Startup Command and Parameter Reference

> ## Filtering Asynchronous COM Events (-filterocxevents)

> Use Filtering Asynchronous COM Events (`–filterocxevents` ) to control the conditions under which you want asynchronous COM events handled.

> Operating system and syntax | UNIX Windows | `-filterocxevents`
> Use with | Maximum value | Minimum value | Single-user default | Multi-user default
> Client Session | – | – | – | –

> An asynchronous COM event is one that is sent by an ActiveX control or Automation object because of an external event, rather than in response to user input. One example of this is the Tick event from the PSTimer. Another is an event signalling the receipt of a message from an external source, such as a control that implements a mail notification system.

> By default, asynchronous COM events are handled when any of the following conditions occur:

> 1. While an application is waiting for user input, such as during a `WAIT–FOR` or `UPDATE` statement.

> 2. While an alert box from a `MESSAGE` statement is on the screen.

> 3. During trigger processing, if the `MultitaskingInterval` parameter is set to a number greater than 0.

> Handling COM events during the second and third conditions might cause random problems in your application, depending on what 4GL code is executed in the event trigger. You use the `–filterocxevents` startup parameter to prevent asynchronous COM events from being handled during the second and third conditions.

Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095