You need to do some analysis on the needs and find the common points. You
will likely find you can work either with a few subclasses, as states group,
or with groups of classes attached to the main class.
If your business does not give time for analysis, you can start with 50
classes and refactor down. If you business will not give time for
refactoring, you are in trouble.
As for the UI, you can create a more dynamic UI that reads the classes, so
you do not need 50 UIs.
BTW, this is always a pain.
The other method is to set up custom fields that can store any old crap you
want. This is common with configurable systems. I would rather do the
analysis and add a few custom fields for the business than adopt this
methodology.
--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA
Subscribe to my blog
http://feeds.feedburner.com/GregoryBeamer#
or just read it:
http://feeds.feedburner.com/GregoryBeamer
********************************************
| Think outside the box! |
********************************************
"GiJeet" <gi****@yahoo.comwrote in message
news:15**********************************@d70g2000 hsc.googlegroups.com...
Hello, I'm working on a winforms app that will be used in stores in
different states and each state can have different data capture
requirements. I want to create a base form for for all the common
data and wish to use visual inheritance to subclass the different
forms that need to capture specific data for each state - but I don't
want to have 50 different subclasses. And I don't want to have a huge
IF statement saying IF NY activate this field, IF FL activate that
field, etc.
Any suggestions on the best way to go about doing this would be
appreciated.
TIA
G