Ocx

Object List Hierarchy Next Object

Definition:

Custom controls with the .OCX file extension that take advantage of the new OLE technology.

Specialized Features:

The following table lists and describes the properties added by Ocx. There are no added methods or events.

---

Properties Use to...

---

OCXClassName Select which OLE Custom Control to become

Automate Access the OLE Custom Control's Automation interface directly

Details:

Ocx’s include specialized controls, third-party custom controls, and versions of standard controls that have been enhanced. 16-bit custom controls with the .VBX file extension use older technology.

To use an Ole Custom Control, first clone the Ocx object, and then set the OCXClassName property to the “classname” (also known as ProgID or Program Identifier) of the Control. Then the new Ocx can be placed on the Controls palette, and hence on a Form. When the Ocx needs to create a window, it will load the OLE Custom Control from the Ocx designated in the registry.

Before .OCX files can be used, they must be registered first by some program such as Microsoft’s REGSVR32.EXE. Once registered, the Ocx object can find and load the Ocx files by “classname” (ProgID).

The Ocx object may hide some properties or methods of the underlying Custom Control (notably those defined on the Control Object). Direct access to the underlying control’s automation interface may be accessed through the Automate property.

---

Note: You cannot use 16-bit VBX’s with Phoenix, which is 32-bit.

See Also: