You may be able to find out what filtering etc. is being applied by doing
one of the following (I'd attempt this myself but my Works system is
elsewhere at the moment):

1.
a. open your mail merge main document
b. start the VB Editor
c. open the Immediate window (it is often already open)
d. type the following commands, one at a time, and copy the results into a
message to post he:

Print Acrivedocument.Mailmerge.DataSource.Name
Print Acrivedocument.Mailmerge.DataSource.Connectstring
Print Acrivedocument.Mailmerge.DataSource.Querystring

Unfortunately, if you are using Word 2002, executing those commands may
cause Word to crash (and even more unfortunately, before it displays the
results). Or you may not have the VB development environment. In that case,
try...

2. If you have a version of Word that can save in HTML format
a. open your mail merge main document
b. save it as HTML format
c. use Notepad to open the HTML document, and look down to see the
mailmerge settings- look for the following, which should be in a single
block near the top of the file

w:MailMergeDataType
w:MailMergeConnectString
w:MailMergeQueryString
w:MailMergeDataSource

Typically it would be the query string that reflects where any sorts or
filters have been defined, but there are other possibilities, e.g. if people
have selected individual records. When Word is merging from Works, it uses
an intermediate file which maes things a bit more complicated.

Peter Jamieson


If you are able to start the Visual Basic Editor in Word while your mail
merge main document is open,
"Charity Event Secretary"
wrote in message ...
Thank you for a thoughtful response. It would be good to find a robust
answer because the database is intended to be maintained by several
volunteers at different locations, most of whom are 'home users'
unfamiliar
with switching between formats. Here's hoping that someone may report
that
they have found out how to unlock the hidden Query Options.
Apropos your suggestion about winding-back Word, I have tried using the
same
Works data file on three different PCs using three different versions of
Word. And the result was identical.
This suggests that the problem lies in the Works file, and perhaps the
thread should be cross-posted?
--
Service Above Self


"Graham Mayor" wrote:

I suspect (though cannot confirm) that the problem relates to the fact
that
the Works database is incompatible with Word and that some
interoperability
has been introduced by the Works add-in which is notoriously
problematical.

You could try rolling back Windows to a date when you know it was working
correctly, but if it was my system, I would uninstall the Works add-in
(see
http://www.gmayor.com/multiple_mail_merge_entries.htm ) and export the
data
to a CSV file and then convert that CSV file in Word to a table, as Word
is
happiest with tables. See
http://www.gmayor.com/convert_labels...mail_merge.htm then change the
table header to match your merge document field names (or re-insert the
new
names)

--

Graham Mayor - Word MVP

My web site www.gmayor.com
Word MVP web site http://word.mvps.org



Charity Event Secretary wrote:
While preparing to print labels from a Works 8.5 database (a process
that has worked successfully many times) Word has suddenly refused to
show the full set of records. Word acknowledges the existence of the
full set but shows only a subset. The remaining records are blank
both in the 'Mail Merge Recipients' box and after a properly
processed merge to a new document. In the latter instance the labels
are there (in other words it is _not_ just one page) but they are
blank.
Invoking the MailHelper button as suggested in other threads reveals
that 'Query Options have been set', but trying to change them reveals
a Filter and Sort dialogue that is blank. And yet the program
behaves as though it is stuck in an earlier Query condition.
This has happened before and I have spent hours copying records a few
at a time into a blank database. This worked in the end, though an
easier method was to save in csv format and reopenthe data. But both
methods required re-defintion of fields and reports.
Has anyone else experienced this symptom? And is there a remedy?
PS I may not be able to read replies for two weeks, but will watch
this space eagerly on my return!