Defining OCX Container Widgets

1. Set the component field's Widget Type to OcxContainer.
2. In the Widget tab of the Properties Inspector, choose the OCX Name property and select the OCX control to use.

   Only e OCXs that are registered with your system are available. Normally, the OCX installation software handles registration of the OCX.

3. Map an OCX property to the value of the OCX field in Field Value Linked To.
4. To map OCX events to interactive triggers, select Use Extended Triggers. Otherwise, select the OCX event for the appropriate trigger:
   • Fire Value Change On (ChangeEvent)—map to the field's valueChanged trigger.
   • Fire Detail Trigger On (AcceptEvent)—map to the field's detail trigger.
   • Fire Async Trigger On (AsyncEvent)—map them to the receiveMessage trigger.

   Note:  Using Extended Triggers is preferred to mapping OCX events to triggers, and much more flexible. However, there are limitations to using extended triggers for OCX events. For more information, see Interactive Widget Triggers for OCX Controls .

5. Click Generate Signature to create a signature of the OCX control.

   The signature enables you to address the OCX methods in ProcScript. You can examine the signature in the Signature Editor.

6. Optionally, click Load License to retrieve the license information from the OCX and encapsulate it into the form component.

   OCX controls are often licensed. To deploy form components that use OCX controls, you need to deploy the licenses as well. Uniface supplies only a license distribution mechanism, not the licenses themselves. You must obtain the appropriate licenses for your OCX controls.

7. Instantiate the OCX control, obtain its handle, call methods on the control, and set properties in ProcScript. For more information, see Using OCX Controls in ProcScript.
8. Test Form Components Containing OCX Controls. For more information, see Testing Form Components Containing OCX Controls.

Related Topics