>Actually, I don't see why the abstract factory has to be data driven with classes.dbf. The information provided in classes.dbf could be accomplished in a class with properties. Then I could subclass it for an application. I know adding properties to a isn't as easy as adding records to classes.dbf but what

Good point... the abstract class could contain a property for every entry in classes.dbf... upon running qstart a subclass of the factory, aFactory would be put into your aapp.vcx.

You could open this class and modify the values of the properties... if you wanted to add some, just add properties. This may speed up processing to, since there is no i/o in the factory.

Of course, this doesn't allow for setting up two or three classes.dbf (aclasses)... Just decide which one to ship, and you have a normal version and a PRO version of your app with that small change.

BOb