Bhavbhuti,

>Okay thanks so I gues 10-20 levels won't have much of a performance impact.

No it won't, unless there is code at each level then it'll take time to execute. But layers of inheritance that don't have any code in a method cost nothing in performance.

>What has me confused is that this class comes from a template folder which is copied when a new app is created, rather than a class heirarchy and in itself contains codes. I have some kind of a mental block in updating the template folder, in the sense if there is a change in the template in the original distribution (chances are very more as now CB has gone opensource) how will I seperate my codes/changes from the original template code/changes the next time round the template is updated.
>
>Generally I attack the i-level classes for changes that I require between all the diff. projects, but this one got me working for each and every project and was pretty routine to do always, thus this thread.

That's the main reason for creating your own layer of classes. So that you can fix/change the classes to suit your requirements and still be able to recieve updates to the framework classlibs.