COM Proxy Interface

Any OLE automation client can make use of a generated COM Proxy. This chapter discusses the interface exposed by a generated COM proxy in terminology consistent with Visual Basic (VB) nomenclature. That is, VB type names are used instead of C++ names.

There is one generated COM proxy for each component. A COM proxy's library name (as it appears in a VB Object Browser) is <component>Typelib. Within each COM Proxy, there is one class (as seen in the VB Object Browser) for each procedure step of the component. For example, if a <component> has the procedure steps READ_EMPLOYEE and UPDATE_EMPLOYEE, there are two classes, ReadEmployee and UpdateEmployee.

Each class in a COM Proxy has a common set of properties and methods that are associated with all COM Proxy classes, and a unique set of properties based upon the procedure step import and export attributes.

See the generated sample code for an example of how an ASP or VB application might make use of a generated proxy. The sample code is placed into the \asp, \vb and \xml subdirectories of your <model-name>.ief \proxy\com directory.