This variable determines precisely when the thin client sends CMD-ACTIVATE events to the server. Under the default setting of 1 (on, true, yes), the client delays sending the event until after the Windows notification routine receiving the event has completed. However, ActiveX events are never delayed. The alternate setting of 0 (off, false, no) sends the event to the server immediately when it is generated on the client.

Acucorp recommends leaving this variable at its default setting because the Windows API occasionally alters actions taken by the program when they occur within the scope of an activation notification. (For example, Windows will sometimes override a set focus call.) Delaying the COBOL program's response to the activation until after the Windows notification routine is complete avoids these alterations.

If you experience an unexplained difference in window activation when running under the thin client, try setting this variable to 0. If this produces the desired behavior, the handling of the CMD-ACTIVATE events by the program is unusual and may not be performing as intended. For example, the EVENT procedure that handles the CMD-ACTIVATE event may be destroying an unrelated window instead of transferring control to the window issuing the CMD-ACTIVATE event.

For more information about the thin client, refer to the AcuConnect User's Guide.