prevent duplicate mailing labels

  • Thread starter Thread starter Kendal
  • Start date Start date
K

Kendal

I am trying to query a client transaction table for
clients with transactions that fall within certain dates,
then print a mailing label for each of those clients.

My query correctly produces a list of all client
transactions that fit the criteria. The labels based on
the query correctly pulls the client address information
from the address table.

The problem is that I get one mailing label _for each
transaction_. So there are several labels for each
client. I need only one label for each client, regardless
of how many transactions each client has.

Can I have my query show only one instance of each
client? Or is there a way to do that in the mailing label
design?

Thanks for any help,
Kendal
 
Can I have my query show only one instance of each
client? Or is there a way to do that in the mailing label
design?

Set the "Unique Values" property of the query to True.
 
Thanks for taking a look at my question. The "Unique Values" property
didn't do the trick. But it's in the right direction.

Instead of showing Unique Values based on the whole query, is there a way to
do something similar for just a single field? In other words, to show
"Unique Values" based only on the "Client_ID" field? I'd like the query to
show me only one transaction for each client. It doesn't matter which
transaction. That way I can print labels for only those clients who have at
least one transaction pulled up by the query.

Thanks,
Kendal
 
Instead of showing Unique Values based on the whole query, is there a way to
do something similar for just a single field? In other words, to show
"Unique Values" based only on the "Client_ID" field? I'd like the query to
show me only one transaction for each client. It doesn't matter which
transaction. That way I can print labels for only those clients who have at
least one transaction pulled up by the query.

Sure. Create a Totals query (by clicking on the Greek Sigma icon).
Group By the ClientID and use First as the aggregate function for
everything else. This will pull an arbitrary field.

Or... just uncheck the Show boxes on any Transaction fields, and set
Unique Values. If you don't show the field it doesn't count as a
distinct value.
 
Thank you! That worked perfectly. Such a simple solution. Yet you
wouldn't believe how much time I spent searching through the Access Help
files trying to figure it out!

Much obliged,
Kendal
 
Back
Top