Design problem updating parameter table

  • Thread starter Thread starter Laurel
  • Start date Start date
L

Laurel

I have a parameter table with three columns, Param_Key (autonumber),
Param_Name and Param_Value. I use this to store all sorts of miscellaneous
single instance data. E.g., Param_Name = "Initialize_Date" and Param_Value
= 1/1/2004....

I can't figure out a way to make a user-friendly form so that each item can
be updated in an environment where I could specify the Param_Name, with,
perhaps, some explanatory text. There is no need to allow additions of new
rows. That's fixed by me. The only structure I can think of is a
continuous form or datasheet view, but that doesn't provide any method for
associating descriptive text with a Param_Name. I had hoped I could use
text boxes, but they don't support updating. Do I need a tiny, tiny subform
for each different row in the tblParameters table?
 
Hi Laurel,

Add a Param_Description field (text or memo depending on verbosity) to
tblParameters. After that, it's a question of interface design.
Possibilities include:

-An ordinary form bound to tblParameters with an unbound combobox at the
top containing the list of Param_Names, and a pair of textboxes for the
Param_Description and Param_Value. When the user selects a parameter in
the combobox your code has the form find the corresponding reocrd,he
description and value appear in the body of the form. The
Param_Description textbox should have Enabled=False and Locked=True so
it can be seen but not edited, and the form should have
AllowAdditions=False.

-Same setup except with a listbox on the left to display the list of
Param_Names.

-A continuous form with textboxes for Param_Name and Param_Value, with a
textbox in the footer to display the Param_Description.

(From your comments in other posts I guess you already know you can use
further fields in tblParameters to store validation information for the
individual parameters so your code can prevent users entering
inappropriate values.)
 
Very clever!!! Thanks!

John Nurick said:
Hi Laurel,

Add a Param_Description field (text or memo depending on verbosity) to
tblParameters. After that, it's a question of interface design.
Possibilities include:

-An ordinary form bound to tblParameters with an unbound combobox at the
top containing the list of Param_Names, and a pair of textboxes for the
Param_Description and Param_Value. When the user selects a parameter in
the combobox your code has the form find the corresponding reocrd,he
description and value appear in the body of the form. The
Param_Description textbox should have Enabled=False and Locked=True so
it can be seen but not edited, and the form should have
AllowAdditions=False.

-Same setup except with a listbox on the left to display the list of
Param_Names.

-A continuous form with textboxes for Param_Name and Param_Value, with a
textbox in the footer to display the Param_Description.

(From your comments in other posts I guess you already know you can use
further fields in tblParameters to store validation information for the
individual parameters so your code can prevent users entering
inappropriate values.)
Click to expand...
 
Back
Top