The second possibility is what I am looking for. In reality, I must deal with at least 6 types (classes) of customers. My present app in FoxDos2.5 has become almost impossible to work with because of the multiplicity of conditional iff's in reports etc. How far have you gotten in your efforts? Is your basic approach to create an instance for each class that may be used in the report and then do something like:
thisclass=iif(....) on the record break
and then in the detail line do something like (thisclass).figureamtdue???

I can see this as still being somewhat messy but definitely better than multiple conditional iffs hidden away in report fields and variables.

I anticipate having much method code for each of my customer classes. How much overhead is associated with having an instance of each class loaded in memory. Is it really the same as having several procedure files loaded? If the base class contains the code for all shared methods, is that code loaded into memory only 1 time or is it loaded for each instance?