irst off, I have NO IDEA what you're trying to say. Second, you must be an
old COBOL programmer (like me), because you like 120 character field names.
I'd get rid of the following part of the field names:
That does nothing for you.
Further down in your post, you start using the term "queues". I'm not sure
in what context you mean that.
In any event, I'd have a Contacts table that lists than name, party,
district number, etc, but then add a code indicating what body they belong to
(i.e State legislature, federal legislature, house, senate, etc.)
I'd create a second table that had all those possibilities, each associated
with a code number, and that code number goes into each Contacts record. When
you link the tables, the code will allow you to pull up the body's
description from the other table.
The way your table is currently created is IMO some very bad design. It is
not normalized properly at all.
Another way would be to have a LegislativeBody table, and assign Contacts TO
that body via another table. Lots of ways to do it, but NOT the way you've
" XXXX@XXXXX.COM " wrote: