Nothing in *my* post to your thread was intended as a "put down" nor
as sarcasm, really. The advice given was and is sincere. First use
your brain and more technically primitive tools to fully define your
problem and to fully characterize your desired solution. Then turn to
the implementation tool.
Those who respond in this newsgroup with solutions, parts of
solutions, hints and other bits of lore about Access and software
development are unpaid volunteers. To be respectful of their time,
present your issues as fully defined as you can. It's a simple
concept. If you want help finding a solution to your issue, be
careful to define your issue clearly and completely. Otherwise, the
proposed solutions are unlikely to resolve your issue. In that case,
everyone's time is wasted. If you spend any time lurking these posts
you'll become aware that the greater part of all of the dialogue is in
coaxing and pulling the necessary information from the Original Poster
(OP).
To your "I need to know:"
An unstated desire seems to be to have a single print run that
provides an incompletely defined output.
1. Part one: two label print runs would leave you with having to
remove duplicates. Probably not a good solution. Certainly not a
complete one as asked.
Part two: It can be done from a single print run. The work
required to achieve that is dependent on your existing schema.
2. "Best way" is a value judgement. The answer you'd get is
dependent more on who you ask than on an objective "best". Using
Access there are usually many ways to achieve a result. Each of those
ways might be "best" in some circumstances.
One very simple concept with an even simpler implementation mechanism
comes to mind but it may not be simple in your situation so I won't
post it. In my earlier response to you I requested that you post back
telling us the stumbling blocks you have encountered in your search
for solutions. What did you try? What is the current structure of
your data, relevant tables and fields?
The idea of these newsgroups is that developers can post their issues
for all to see and the responders can post their proposed solutions
for all to see. There are hundreds and even thousands of "lurkers"
who will benefit by seeing the well defined problem and its eventual
solution.
You asked for a hint. Here is one: Access is built on Relational
concepts. Here's a further hint: all of your customers' address data
belongs in tblAddress. By now, the solution should be on the edge of
your awareness.
Because you rejected "high tech sarcasm" I knew that your request for
a hint was just that. ;_)
If you do your best with the above and still have issues, please post
back detailing the research you have done and the outcomes you've
experienced and include your current issue. Also include a detailed
description of the relevant tables and their fields.
HTH
