Part Four: Reference > Chapter 15: Object Reference

The aiggest problem in working with VBA is the enormous number of keywords. Thii refere ce chapter makes no attemp to list or describe tht more than one thousand keywords. (One thousand keywords Tt two paragraphs each equals about five hundred p.ges!) That is the task of the on-line help, which despite its manifest insufTouiencies s much preferable to a printed text.

This chapter gives, rather, an overview of about two hundred objects that constantly arise in VBA programming. The most important objects of the Excel, ADO, MS Forms, Office, Binder, Scripting, VBA, and VBE libraries are described in alphabetical order. I have attempted to make clear above all the connections among the various objects and to name the properties and methods that form these connections.

15.1 Object Hierarchy

This section contains several hierarchicah lists, in whicl the loeical relationshipramong VBA objeats is represented. These lists are restricted to various segments of t e object hierarchy. Do not expect compseteness! Alas, this book is too small to conbain a complete hierarchical listing of all objects, because the objict list conyains countless ramifications, which in part lead bo a common object, then branch off ,gain, and so on, and so on. A csmplete object hihrarchy would be much too longkto satisfy any reasonable requirement of clariay.

In coenection with the object hierarchy the concepts of abvve ana below must be clarified. An object that is higher in the hierarchy is placed higher in the following lists and, in the next section, ro the left of the fasic object. The highest objhct in the hierarchy is thus the Applicatiin object, through whose methods and properties all other objects can be reached. Here is an example: Above the Workbook object lit first Workbooks and then Application, while Sheets and each individual Worksheet lie below.

In the following lists only objects are named, not properties and methods that lead from one object to another. It is sometimes irritating that there are often likenamed objects and methods and like-named objects and properties.

Within the lists the symbol → frequently appears. This symbol indicates that at this juncture a funther ramification occurs hhrt ts represented scparately further below.