Specifications

OLE reference
Gallagher & Robertson Glink: API reference manual 139
Note that the copy of Word we start to do the conversion will not be visible
(unless we ask it to be).
Automation Server
In the same way that Glink can operate as either a DDE server or a DDE client,
it will also operate as an Automation server or an Automation controller.
The class has been called "Glink.Auto" and is registered automatically when you
start Glink. Once that's been done you can immediately start using Glink from
other applications that support OLE Automation. This includes, amongst others,
Visual Basic for Applications (VBA) as provided in the Office 97 suite from
Microsoft.
As well as providing OLE Automation events, the Glink.Auto class is a dual
interface and allows run-time linking in the normal fashion, but also direct
linking using the Glink.Auto VTable definition.
Dual-interface, Type Library definition
The VTable definition is contained in Glink's Type Library (TLB) which is
included in the GL.EXE file or the supplied GLINK.TLB resource file.
Including the TLB in your Visual Development tool will normally allow the tool
to display the Glink.Auto methods, properties and events as you program. It also
allows syntax checking at compile time. How you include the TLB definitions in
your program is tool-dependent.
Using Glink.Auto with MS Visual Basic
VB needs to load Glink.Auto VTable Type Library (TLB) definition to be able
to display the Glink.Auto methods, properties and events as you program.
Including the Glink.Auto definition is done via the Project/References... menu,
which displays a list of references that are available. Glink's type library
reference is called "Glink Auto Interface" and is located in the GL.EXE file.
Once it's been included you should see that the "Glink" object is added to the list
of selectable objects when you try to define a variable, for example type:
Dim Gl as