S
Shannon
A Ballot shows a candidate for each piece of property they
own. Some of the candidates own multiple properties, but
I want their name to show only once.
To further complicate things, they are already grouped by
district and all the district's candidates print per
page.
The candidate can have their name more than one district,
but only once for each district.
Now, the clincher. The spouse can be listed as a
candidate if the couple owns more than one property in a
district. The couple is in the computer with a MemberID
that they share. They use that same MemberID for all the
properties. Each property has a DesignatedVoter field for
which they choose either spouse.
The query is grouped by District and sorted by Lotblk (or
address) but could just as easily be sorted by Designated
voter (but it would be yucky because they are entered by
the full name as in John Doe) where John Doe would be
after Ann Zarda.
This may be too much information, but the main idea is to
have only one DesignatedVoter per spouse per MemberID per
District.
own. Some of the candidates own multiple properties, but
I want their name to show only once.
To further complicate things, they are already grouped by
district and all the district's candidates print per
page.
The candidate can have their name more than one district,
but only once for each district.
Now, the clincher. The spouse can be listed as a
candidate if the couple owns more than one property in a
district. The couple is in the computer with a MemberID
that they share. They use that same MemberID for all the
properties. Each property has a DesignatedVoter field for
which they choose either spouse.
The query is grouped by District and sorted by Lotblk (or
address) but could just as easily be sorted by Designated
voter (but it would be yucky because they are entered by
the full name as in John Doe) where John Doe would be
after Ann Zarda.
This may be too much information, but the main idea is to
have only one DesignatedVoter per spouse per MemberID per
District.