may be jumping in without a complete picture. My fault, not yours.
It seems that John is trying to nudge you gently along the path to a
complete solution. Suggest that you accept a partial solution and
then hope that John will pick it up again or post a new thread with
the new / remaining issue.
Those cotton-bickin' traps from Microsoft have to go. The values for
the races are in a table. That's exactly where they should be and
that table is quite appropriately referred to as a "Lookup Table"
however, lookup tables have absolutely nothing to do with "Lookup
Fields" which are an abomination. Lookup tables are not a separate
kind of object from a regular table. They are simply regular tables
used to store more or less stable lists of things for purposes of
"lookup" via a combobox.
Assuming that your primary key of tblRace is an Autonumber datatype,
change the field type of field "race" in your primary table to Long
Integer. If it doesn't already have an Autonumber Primary Key, please
add one so that this example will work. On the form with which you
manage this information, make the control for "Race" a combobox based
on a query on tblRace. When you design the query for the combobox,
tell the Combobox wizard that you want to lookup a value and then let
it hide the ID field. With your combobox design complete, return the
form to run mode. Then, when you choose a race from the list it will
be placed in the combobox. It's ID will be placed in the control ant
it's value will be written to the field in the underlying table. You
will explicitly be doing what the Microsoft trap did for you under the
hood. Now you will expect a query on that table to return a number
rather than a race. You can write queries that can apply that ID
value to return the text value of the race in question. No problem.
Once you have done that you can press on with creating Totals queries
to get the numbers of genders, races and whatever else you need to
If I've misunderstood then my apologies to all concerned.
"malpho" < XXXX@XXXXX.COM > wrote in message
news: XXXX@XXXXX.COM ...
would be able
< XXXX@XXXXX.COM >
exception of 1
Nine of these
to look. You