471,330 Members | 1,835 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,330 software developers and data experts.

Pattern for varying number of fields???

Hi!
Im migrating an application from ASP to ASPX. Its a webapplication like
TestDirector ( TestDirector is a single, Web-based application for all
essential aspects of test management Requirements Management, Test Plan, Test
Lab, and Defects Management).

Many reports can be created, like error reports, statistics etc. These
reports are very customizable in that the customer (eg a testleader) can use
a number of default fields, remove some or all of those, add new fields.

In todays ASP solution we read the database and get whatever fields the
customer has for that perticular report, and loop the recordset and build the
report. All in a very functional way.

Because this is a very flexible solution, I wonder what good objectoriented
practices to apply in this case where the fields I get from the database can
vary very much.
What do you recommend. Save every field as a class? Is there anything to
gain on a OO solution?

What experiences do you have from dynamic webpages where the customer can
decide what content to see? Is there a pattern for this?
Regards
Jesper D
Dec 30 '05 #1
0 774

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

2 posts views Thread by Grumfish | last post: by
4 posts views Thread by Nicolla MacPherson | last post: by
9 posts views Thread by Hasan O. Zavalsiz | last post: by
1 post views Thread by Eric | last post: by
34 posts views Thread by Steven Nagy | last post: by
19 posts views Thread by konrad Krupa | last post: by
reply views Thread by rosydwin | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.