Cheryl,

I think you mean "relational database design" or "normalized tables" rather than OOP.

Do I have this right: 50 states, a special report format for each one, each special report has 15 areas to fill in?

So the tables could be:

State_Report table:
StateId, ReportId (associates state with a report, a state could have several reports and therefore several lines in this table)

Report_details table:
ReportId, DetailNumber, DetailInfoMemo

Then you won't have a fit when they want to add the 16th detail item to a report!


>I have a template form report that we have designed. Depending on the state the insured is in, a form table is read and the appropriate information is then entered into the needed 15 areas. When I originally created the table, I have one record for each form number and then 15 different memo fields for each area. I realize this does not follow good OOP design.
>I now have the opportunity of changing this format if someone can help me create a better design. I tried but to no avail. I know that sometimes we cannot use the rules of OOP which is fine. But since I'm relatively new to VFP and OOP I thought I would ask the expert for some advice. Thanks for your help.