Bernard

I tend to have a "BaseClass" of form, with not to much formatting, functionality, restrictions, etc.

From that, Subclassed to, say, a dialog class (ex. is that it's fixed size)
From the base class, say, a paged form for data entry, etc.

You can keep on building the extra features of each class on a previous class. This way, if you find you've "gone too far" for a particular need then you can always back-track to a previous, less restrictive class, but still have standard features that ALL your forms will have, such as font size, colour, etc.

Introduce methods higher up the "food chain".

In essence, there's nothing to be afraid of and evrything to gain.

Many people will tell you to steer clear of formsets as they are a pain in the butt.

HTH

Terry

>Hi all:
>
>This is the first time I am using form classes. In my application, I decided to use several form classes that I reuse for many different forms. Sort of cool stuff and I think would make things easier to maintain.
>
>My worry is, what are the pitfalls of using such form classes? Is there anything that I need to look out for? Sorry my question may be quite general in scope, but my purpose is to be able to foresee what problems I would probably hit, and if it is really feasible to do so in the first place. I am just trying to avoid the scenario where I am halfway into a project and find out that what I am doing does not work at all; I have had enough of such experience. :)
>
>I would appreciate all the help I can get.
>
>Thank you.