>Thanks Hilmar. Actually I have a requirement where even though clients want one or both, there are customization to the screens & reports which is something only they like. I such a case I was hoping to develop a basic application for all and start from there when a job arrived.
>
>Any suggestion, first hand experience in such a case?
No first hand experience. I suspect that in this case, you have to subclass, after all, as you originally suggested.
This would require you creating two main folders: one for the "generic" project, one for a specific client.
In the folder for the specific client (or specific configuration), you have to subclass all your classes, one by one.
This will be a lot of work at the beginning, but I don't see any other way. And once you did this, you can make global changes (that affect all clients, through inheritance), and others that affect only a single client.
I understand that the CodeBook Framework uses this basic principle for a slightly different purpose.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
