OleControl Class

The OleControl class allows attachment of objects that are actually edited or controlled by other applications. For example, a Word document, an Excel spread sheet, a video clip, or a Paintbrush picture can be stored in Jade, but editing or playing the object invokes the controlling application.

The OleControl class handles any objects for which an Object Linking and Editing (OLE) Server is registered in the database of your operating system registry. An application that is capable of being an OLE Server has a .reg file associated with it. To load the registration information, double‑click on the .reg file in File Manager or Explorer.

The following objects can be handled by the OleControl class.

The OleControl class is not supported on forms defined as web pages and is ignored when HTML is generated. For details about interfacing to OLE, see "Interfacing to OLE 2.0", in Chapter 2 of the External Interface Developer's Reference.

The Jade extract process extracts a definition of the OleControl object (as it does with other controls painted at design time when the form definitions are extracted) but it does not extract the user data associated with the control. It is your responsibility to extract the user data and load it into a deployed database, if required.

For a caveat on the use of SVG files when printing OleControl controls, see "Portable Printing" under "Printer Class", in Volume 1 of Chapter 1 of the Encyclopaedia of Classes.

Transparent sibling controls are always painted before an OleControl control, regardless of their zOrder settings. It is not possible to handle the painting of transparent controls in the correct zOrder when some controls are directly painted by Jade and others are painted by Windows separately.

For a summary of the constants, properties, methods, and events defined in the OleControl class, see "OleControl Class Constants", "OleControl Properties", "OleControl Methods", and "OleControl Events", in the following subsections.