>Yes, you have the point exactly. Thanks. Let's say I want to create a pricing object for telephone calls anywhere in the world. This object is only valuable to one client so it should be in the 3rd level for sure. I'm not sure what value there is to having its parent be anything but the "custom" class from level 2 which is subclassed from _custom from _base.vcx. I could put on level 2 the price object without any code in it in case the company gets a contract with another carrier and things must be priced one of two ways. You are right that I am at that place where I am trying to decide if every new class needs 3 levels or not.
>
ok so if I understand you correctly your levels layout is
level 1 - FFC
level 2 - general (i.e. all projects)
level 3 - specific (per project)

in this case every object that will be used in a single object should be based on level 3 "base" classes and any object that will be used in many projects (or shows a good optential for that) should be built using level 2 classes
remember that you can always re-define an object and re-arange it later.. :)

Arnon