Rather than Check boxes, why not drop down lists? If you ever decide to add
another option, then the drop down list can be easily modified. Adding a new
check box will not be as easy.
John. Visio MVP
From: MS_Access_Professionals@yahoogroups.com
[mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Dan Fielding
Sent: Friday, May 11, 2012 8:37 AM
To: Yahoo Access Group
Subject: [MS_AccessPros] Too many checkboxes?
I'm wondering if it is possible to have too many Check Boxes even though
that is the only way I can envision it. By way of an easy example, let's
say I want to deal with taking pizza orders and keeping track of things. I
could have the following:
Pizza Size (small, medium, large)
Pizza Toppings (anchovy, mushroom, extra cheese, pepperoni, sausage,
pineapple, ham, onion, etc.)
Other Items (bread sticks, garlic bread, cinnamon dessert sticks, etc.)
Now, I design a Form with three columns. I figure the Pizza Size would be
an Option Buttons group. The Pizza Toppings and Other Items columns would
all be Check Boxes since it would be possible to want multiple choices and I
would have to account for all possibilities. Just to be sure to capture all
possibilities I might want to create another field called NoExtras which
might also be a Check Box.
In my scenario I would probably want NoExtras to be hidden and code would
determine if it were checked, or not. So, I would have to create code to
check each Check Box in Pizza Toppings and Other Items. If none were
checked I would want to programattically check the NoExtras box so I could
test for that condition, as well.
My first question is, other than a series of individual If statements that
checks the condition of each individual Check Box in the two columns is
there a better way to look at all of the Check Boxes at at one time in order
to determine if any are checked?
Actually, in anticipation of what you might be thinking, is this whole
approach of many Check Boxes and testing each one just a crazy way to go
about this in the first place? If so, what other general designs would you
suggest.
Often the hardest part for me when creating a database is figuring out a
reasonable approach. Part of it is determined by what I know I'm able to do
with an unfortunately limited skill set, and another part is always
second-guessing what I'm doing as I'm doing it and wondering if I should
have headed in a different direction.
Thanks for any thoughts you'd be willing to offer on this.
Dan
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
Tidak ada komentar:
Posting Komentar