I'm trying to model my business objects using Mere Mortals and I have a design question. I have a parent/child relationship between two tables, where the parent table contains just a key and a description of the "type" of the defferent child tables - "person", for example. I had considered having an "entity" business object, and a "person" business object which inherited from entity. My question is, how could this be implemented using MM? It seems like a reasonable desing pattern - would this not be considered a good technique?

The problem I'm facing is this: because business objects in MM have their own defined table and primary key, it's a problem trying to inherit one business object from another, where each business object must deal with it's own table. For example, if I create business object "A" which deals table "TableA", and then inherit from "A" to create "B", where "B" deals with "TableB", the TableName property will remain "A" unless I change it to "B". That is, I need "A" to continue to deal with "TableA", and "B" deals with "TableB". Perhaps an inheritance model is not appropriate for this kind of relationship...

I'd be interested in hearing suggestions about different design patterns for related business objects.