Considering the CaseWare IDEA Object Model
Up to this point, you've been looking at particular tasks that IDEAScript can perform. Each of these tasks relies on one or more objects to accomplish the work. The task defines what to do, while the object defines on what to do it. Your code defines how to perform the task using the object resources you provide.
There's a consistent relationship between these elements and you need to know how they work.
Objects don't simply exist by themselves. Consider an apple. The apple may be a single object, but it originally exists as part of a tree object, which is part of an orchard object, which is part of a farm object, which is part of . . . well, you get the idea. Objects are related to one another. In order to use a particular object effectively, you must know how that object is related to other objects. In short, you need to know about the object model, which is a representation of the relationship between various IDEAScript objects.
This chapter breaks the object model into pieces to make it easier to understand. Of course, before you can truly understand the object model, you must know more about objects, so that's the first topic discussed in this chapter. You discover that objects have certain features and that the way these features are implemented determines the functionality of the object.
Once you understand the basics of the object model, the chapter helps you understand the specifics of tasks and direct database manipulation. ...