Jim,

Quick question on "Effective Techniques".

In chapter 5, the timecard example, no tables are used in the form only views. Is there any reason for the read-only type view, such as the basis for a combo that shows all employees, other than to simplify matters if the data get upsized to SQL Server, for example.

Thanks,

Pf

>Aiko,
>
>An abstract class is one that will NEVER be used to create an object. Its main purpose in life is to define an interface (Methods and properties) for a whole group of subclasses. Abstract classes seldom have very much code in them, they are only defining the interface for the subclasses that will cotain the code.
>
>A concrete class is one that IS intended to be used to create objects. Concrete classes often have a fairly large amount of implementation code in them.
>
>Example: A form class heirarchy
>
>fmrBase: Adds methods for MoveNext,MovePrevious, MoveTop, MoveBottom
>
>fmrOneTable: Adds code to the above methods for moving when only one table is involved
>
>fmrOneToMany: Adds code to the Move* methods to move the record pointer when a one to many relationship is involved
>
>In this example, frmBase is an abstract class while frmOneTable and frmOneToMany are concrete classes.
>
>The purpose of frmBase is to provide the interface design, that is the names of the methods and the parameters that they accept. By designing the class structure this way you insure that all forms will have the same set of methods so that your buttons and other controls can be coded to interact with the frmBase interface and they will then work in any form you put them.