Mail Merge Headache (1 Viewer)


Registered User.
Mar 15, 2016
Hi Guys

Can anyone help with my mail merge headache?

I had planned to do a mail merge starting with a Word main document and an Access database query as the data source, then moving into Outlook as the mail handler.

In preparation, I created the Access query which filtered out all but the four fields of MemNumber, Title, LastName and e-mail address. Although the query contained multiple criteria, it was neither a parameter query nor an action query - its function was simply to identify members who had e-mail but who did not subscribe to the e-newsletter.

The problem arose when, from the Word 'Mailing' tab, choosing ‘Select Recipients/Use an Existing List’ the list of available objects presented did not include the filtering query.

Can anyone suggest the likely cause and a solution?

Your help would be much appreciated.

Hmm, mine only shows me queries and any local tables.?
You can also filter within the merge?
As an alternative approach, have a look at Albert Kallal's super easy mail merge which is all controlled from Access.
A Web search will give lots of hits to this code. Very easy go use and works well
Thanks guys. I'll see what I can make of all of the responses.
There is no SQL as the source. The question involved a compiled. Library that I could reference in my Access program. Thanks
I think that Word cannot "see" queries that require Access to be loaded such as those that reference form fields. I personally don't like Mail Merge so I've attached a rudimentary example of Word automation that even shows how to embed a child table so you could use the concept to make something like an invoice where you have parent and child data. The description in the example tells you how you should probably implement the solution rather than using the example as is since it becomes tedious to have to hard code all the bookmark names. In the apps where I have had to automate Word, I've created cross reference tables to map fields to bookmarks by document. The xref defines the data types of fields so that numbers and dates can be formatted correctly.


Yeah that's kind of the road I was going down - and there are a few other things that OLEDB cannot interpret properly that might cause his original problem. Was hoping OP would post the query so we'd know.

Users who are viewing this thread

Top Bottom