Second Class User Objects

Its interesting how when you fix one thing, other things become clear.

The phones in PhoneBook1 should really be second class user objects. But todate CompStrm has not supported second class user objects. It needs to.

Now that we have external properties, it is easy to define second class user objects. These are well knowns that are not in a data set, but are still referenced by an external property. So in the case of a person in Phonebook1, the person file should be in the phonebook dataset. The phone is then "in" a person. Similar rules apply--a phone can be referenced by external properties from more than one file. For that matter, a phone file could also be in a dataset as well. No reason why a second class user object can't also serve as a first class user object.