Specifications

CHAPTER 17 Using OLE in a Report
Users Guide 491
Create From File
Use the following procedure if you want to link or embed the contents of an
existing file as an OLE object so that it can be activated using the application
that created it. Most of the steps in this procedure are the same as those for
embedding a new OLE server object.
A server application must be available
You (and the user) must have an application that can act as a server for the type
of object you link or embed. For example, if you insert a BMP file, it displays
because an application that can handle bitmaps is installed with Windows. If
you insert a GIF or JPEG file, it displays only if you have a third-party graphics
application installed.
❖ To link or embed an existing object using the Create From File tab:
1 Select the Create From File tab.
2 Specify the file name in the File Name box. If you do not know the name
of the file, click the Browse button and select a file in the dialog box.
3 To create a link to the file, rather than embed a copy of the object in the
control, select the Link check box.
4 Click OK.
The OLE object is inserted in your report and the OLE server is activated.
Depending on the OLE server and whether or not you have already
specified how the OLE object will use the report’s data, the object might
be empty or might show an initial presentation of the OLE object. Close
the server application and, if you are inserting an OLE object in a report,
specify the object’s properties (see “Specifying properties for OLE
objects” on page 492).
Insert Control
Use the following procedure if you want to insert an ActiveX control (OLE
custom control) in the report.
❖ To insert an ActiveX control using the Insert Control tab:
1 Select the Insert Control tab.
2 In the Control Type box, highlight the ActiveX control you want to use, or,
if the ActiveX control you want has not been registered, click Register
New.
If you select an existing ActiveX control, you can click Browse to get
more information about it. ActiveX controls are self documenting.
InfoMaker gets the property, event, and function information from the
ActiveX control itself from the registry.