• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 186
  • Last Modified:

access query results will not show in mail merge document

Query X produces 10 rows. Word Merge shows 10 rows.
Query Y produces 5 rows. Word Merge shows 0 rows.

Query X and Y are same object, just with different criteria.

The

Anyone else seen this happend before ?
0
shelbyinfotech
Asked:
shelbyinfotech
  • 3
  • 2
  • 2
1 Solution
 
Rey Obrero (Capricorn1)Commented:
how do you merge "Query Y"?
use the same procedure you used with "Query X"
0
 
shelbyinfotechAuthor Commented:
Yes, in fact its the same query, only changing criteria
0
 
SimonCommented:
Is there any filtering of the data going on withing Word? If the mailmerge document has existing filters they may be excluding all the records returned by Query Y.

It would help if you could describe how your access query results are being used by Word. Are you using the query as the datasource for the merge, or are you passing the query results to Word programatically?

The specific results are being suppressed by a filter in Word is my best guess.
0
Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

 
shelbyinfotechAuthor Commented:
No filters set in Word
0
 
SimonCommented:
Are you _Sure_ about the filtering in Word. In 2010 at least it is a little odd. You can't revisit the previously defined filters, the dialog appears as blank, but the filters have been added to the query string that you can see if you close and then re-open the merge master document. See attached screenshot.
i.e. the filters are still applied even though the dialog doesn't show any. I've just tested that.

If it was me, and the above wasn't the case, I'd try new query variants to see if I could identify a case where query z returns 20 rows but the corresponding merge produces 1-19 rows. That makes it easier to narrow down the value in a particular record that's causing the glitch.
EE-28569327.jpg
0
 
Rey Obrero (Capricorn1)Commented:
upload  a copy of you db
0
 
SimonCommented:
You might also like to try  this MS Word Macro that prints the datasource fully qualified name and querystring to the immediate window. Useful because Word just tells you the name of the datasource and not the path.
Sub Mailmerge_ListOpenDocsDataSourceAndQueryString()
MsgBox "This lists datasource file path and querystring for each open document to the VBE immediate window", vbInformation
Debug.Print vbCrLf & "Mailmerge_ListOpenDocumentDataSources running @ " & Now()
For Each d In Application.Documents
Debug.Print
d.Activate
If d.MailMerge.DataSource.Name <> "" Then
    Debug.Print d.Name, d.MailMerge.DataSource.Name
    Debug.Print d.Name, d.MailMerge.DataSource.QueryString
Else
    Debug.Print d.Name, "NOT A MAILMERGE DOCUMENT"
End If
Next
Stop
End Sub

Open in new window


To use, go to the Visual Basic Editor in Word, add a new module and then paste this in.

---

If I'm on the wrong track here, please tell us more about how you are doing the merge and how the criteria are set in the queries - are they hardcoded or parameters supplied from a form or elsewhere?
Are both queries in the same database file?
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

  • 3
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now