There are definitely problems with filtering with some types of data source.
(whcta are you using?) If you click the drop-down at the top of one of the
columns in the Mail Merge Recipients dialog box and select Advanced, you
/may/ be able to see what Word is doing - sometimes, for example, it
duplicates the last condition in the list that you can enter there.
However, Word complicates things by using two different methods to filter.
If for example you use the drop-down to select a particular value (say,
Country="UK"), Word generates a bit of SQL like "WHERE (Country = "UK" )"
and uses that when it gets the data from the source. But if you
check/uncheck individual entries, Word just sets a flag internally for each
record selected/unselected and remembers to include/exclude it in the merge.
I'm not sure that that helps you, but if you are using the second method, it
might be worth seeing if using the first method instead works better.
Otherwise, re-connecting to the data source is actually likely to be the
simplest way to clear out the old filter conditions. However, if you are
always using the same source, it may make sense to record a VBA Macro that
closes the source and re-opens it, and assign it to a toolbar button. That
way, you should be able to restart with a single click.
Peter Jamieson
> Hi
> i have a mail merge document which I want to use over and over again. But
[quoted text clipped - 18 lines]
> need to then sobeit but it seemed a bit silly.
> Yve
Yve Ke - 07 Sep 2006 11:11 GMT
Yes, thank you that was extremely helfpul. What happens is that when i
re-open from the last time it was used it would launch an sql statement which
I accept. Then the link will not go away, no matter how hard I try. So I
have done as you have said = a refresh button on the toolbar to relink every
time. It sees ok now and very user friendly.
Yve
> There are definitely problems with filtering with some types of data source.
> (whcta are you using?) If you click the drop-down at the top of one of the
[quoted text clipped - 41 lines]
> > need to then sobeit but it seemed a bit silly.
> > Yve
Peter Jamieson - 07 Sep 2006 11:35 GMT
You can probably get rid of those SQL security questions, and it may improve
things in general. But there are security implications. See:
http://support.microsoft.com/kb/825765/en-us
Peter Jamieson
> Yes, thank you that was extremely helfpul. What happens is that when i
> re-open from the last time it was used it would launch an sql statement
[quoted text clipped - 63 lines]
>> > need to then sobeit but it seemed a bit silly.
>> > Yve