Configure editable form fields?

[dm_dal]

I'm looking for some feedback or for someone to point me in a good
direction.

We have a web application that consist of many forms. Some of our clients
have asked if we can configure the app in such a way as to allow them to
turn on/off the editable nature of certain form fields.

ie: Say the form has 10 fields in it, one of which is a field for the users
birthdate. Some clients want the user to be able to change their birthdate,
and some do not.

What's the best way to set this up? Obviously, we could setup config tables
in the db that correspond to all form fields in the app and then mark in the
db for each client whether or not the field is editable, but this seems way
too db intensive. Any thoughts?

dmy

[Anachostic]

I think the answer depends on knowing all the numbers:

How many clients/visitors/pages/controls are we talking about?

I think storing the locked/unlocked fields in a database is a perfectly
valid solution, provided the database is normalized well. I could envision
querying a table passing the clientID and PageName and retrieving the
control names to mark read-only. Or not read-only (whichever returns the
fewest results.)

"dm_dal" <RE******************@yahoo.com> wrote in
news:uo**************@TK2MSFTNGP09.phx.gbl:

I'm looking for some feedback or for someone to point me in a good
direction.

We have a web application that consist of many forms. Some of our
clients have asked if we can configure the app in such a way as to
allow them to turn on/off the editable nature of certain form fields.

ie: Say the form has 10 fields in it, one of which is a field for the
users birthdate. Some clients want the user to be able to change
their birthdate, and some do not.

What's the best way to set this up? Obviously, we could setup config
tables in the db that correspond to all form fields in the app and
then mark in the db for each client whether or not the field is
editable, but this seems way too db intensive. Any thoughts?

dmy