Represented in the object model below is the access path to objects. At the top-level of the hierarchy is the System object; it must be retrieved before any other objects. Similarly, a Session object must be retrieved before a Screen object. Subordinate objects of one type, like Screen, are returned by a property or method of another type object, like Session. Objects returned in this way are referred to as sub-objects.The shaded objects represent entry points into InfoConnect Enterprise Objects. You can start the System object with the CreateObject function. A more direct way to start a session, however, is by retrieving a Session object from a file with the GetObject function.Also represented in the object model are collection objects -- Sessions, QuickPads, and Toolbars. A collection object manages a set of related objects. For example, the Sessions object manages one or more open Session objects.