Albert:
Thanks again for taking the time to provide such a thorough solution.
Regards,

--
Rich Locus
Logicwurks, LLC


"Albert D. Kallal" wrote:


"Rich Locus" wrote in message
...
Albert:
So, if the main table had two records, key 200 and 201, then the States
table would look something like this:

CA 200
OR 200
WA 200
NY 200

CA 201
MN 201
AZ 201

And so on.

Does this seem reasonable?

You are right on the money. The issue is that the proper relation would say
to use a sub-form. that sub-form would likely have the FK (foreign key) as
standard long value column. (the above column to hold the 200 and 201 in
your example). The combo box would have to be feed by a either a value list,
or better yet a table that holds all of the state abbriviations. The user
could type in the state, but clearing a combo box is much easier. Because a
sub-form always shows an extra line, then the user would click on combo box,
select state, then click on the next new line combo box below and again
select sate. it goes quite fast, but it still not quite as nice as that
built in check box. If your list is not long, say only about 10 choices,
then a un-bound listbox with code behind to "toggle" or highlight or un-high
the selections works well. You can see a screen shot of that he

the 4th screen shot here shows this:
http://www.members.shaw.ca/AlbertKal...erFriendly.htm

However, for 4-5, then that new cool built in combo works well. However, for
50 states, it actually quite HARD to scroll and select. I think the combo
box idea above in a sub-form will actually be faster, and the user would
have a choice of 100% keyboard. if you setup the record cycle settings
correct, then the user can hit tab, and type in the state in addition to
using the mouse clicks. So, in your case because this is a long list of
states, a standard combo box likely is better then the multi select combo
box (it too hard to scroll through the long list to just select one state).

Keep in mind that the table of states that drives the combo box is just a
table to save the user some time typing

So, you have your main table, then

tableListOfStates the above table and example you talking about.

And, then the optional 3 table to drive the combo box if you choose to have
a combo box in place of the user typing in the state name. (but, user could
use combo drop down, or just type right into that combo box).

Remember, those combo boxes work well in continues sub-forms as the "grid"
link in the previous post shows.


--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada