OK, Calvin ---

You're going to have to be more explicit. There may be mixed metaphors here: You were talking before about a grid and a report. These are, by nature, populated by tables. I can see a customer object from a Cust1 or Cust2 class representing a row in the customer table but I don't see the relevency to a report or grid where you cannot report classes or (even if your customer objects hold mutiple rows as a collection) anything *but* table based information.

>Cust1 and Cust2 are customer classes. All customers are in the Customer table. The question is how do I call the ClassMethod code for customers of different classes in a report without continually creating new instances of each class. I guess this deals with the 'poly' aspect of classes.