 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
| HomeDiscussionsAccessExcelInfoPathOutlookPowerPointPublisherWordDirectoryUser Groups Related Topics Outlook ExpressInternet ExplorerWindowsMS Server ProductsMore Topics ... |
MS Office Forum / Word / Mailmerge and Fax / May 2006Skip Record If?
Hi, I'm trying to set up a mail merge for labels in which there will be a column in the data source saying either "Yes" or "No" net to each person's name. For the type of mailing I am currently doing I want the people with "No" to be skipped and not have a label printed out. I was trying to do this using "Skip Record If", but this doesn't seem to work. I've tried it in both Word XP and Word 2000 and I can't get it to work right. I am also using a "Next Record" field in the label set up. Are these two fields incompatible with each other? Something I read in Word 2000's online help seemed to suggest that they are. If so what would be the best way to do this? Any information would be greatly appreciated. Thanks! Hi =?Utf-8?B?Qg==?=, > I'm trying to set up a mail merge for labels in which there will be a > column in the data source saying either "Yes" or "No" net to each person's [quoted text clipped - 5 lines] > with each other? Something I read in Word 2000's online help seemed to > suggest that they are. If so what would be the best way to do this? Word 2000: click the "Mail merge..." button on the mail merge toolbar. Click "Query options". Set up a filter to merge to only those records where this particular field is "Yes" (or "No"). do NOT use Skip If; but you will need the Next field in all labels but the first. Cindy Meister INTER-Solutions, Switzerland http://homepage.swissonline.ch/cindymeister (last update Jun 8 2004) http://www.word.mvps.org This reply is posted in the Newsgroup; please post any follow question or reply in the newsgroup and not by e-mail :-) Hi, Cindy, thanks for your response. :) I tried this approach in Word 2000 and it worked. :) How would you do it in Word XP? I didn't see the exact same option there. Would you use the mail merge recipient list feature? Thanks in advance for any help or information. > Hi =?Utf-8?B?Qg==?=, > [quoted text clipped - 22 lines] > This reply is posted in the Newsgroup; please post any follow question or reply > in the newsgroup and not by e-mail :-) Hi =?Utf-8?B?Qg==?=, > I tried this approach in Word 2000 > and it worked. :) How would you do it in Word XP? I didn't see the exact > same option there. Would you use the mail merge recipient list feature? You can go this route, yes. Click the arrow next to a field name, then choose "Advanced". You'll find the same Query Options dialog box behind that :-) Your other option would be to pull the Mail Merge... button out of Tools/Customize/Commands; Category "All commands". Cindy Meister INTER-Solutions, Switzerland http://homepage.swissonline.ch/cindymeister (last update Jun 8 2004) http://www.word.mvps.org This reply is posted in the Newsgroup; please post any follow question or reply in the newsgroup and not by e-mail :-) Hi, Cindy, I just wanted to say thanks for the information. I tried what you suggested in Word XP and it worked fine. :) Thanks again! :) > Hi =?Utf-8?B?Qg==?=, > [quoted text clipped - 15 lines] > This reply is posted in the Newsgroup; please post any follow question or > reply in the newsgroup and not by e-mail :-) Hello, I have tried to use the function you listed below and I got an error message saying that 'Word could not parse the query into a valid SQL string'. I don't know what to do next. I am trying to get a letter not to print if one field = "A" and another field = "DOWNGRADE TO STANDARD COVER" Can you suggest what I might be doing wrong? I have tried using 'SKIP IF' however I don't know if multiple SKiP IF statements in a document will work, so the filter function seemed a better idea. Thanks. Chris > Hi =?Utf-8?B?Qg==?=, > [quoted text clipped - 22 lines] > This reply is posted in the Newsgroup; please post any follow question or reply > in the newsgroup and not by e-mail :-) There is no reason why two SKIPIF statements immediately following one another at the start of the letter should not work as you intend and worked satisfactorily in my tests here. {SKIPIF {Mergefield field1} = "A"}{SKIPIF {Mergefield field2 \*Upper} = "DOWNGRADE TO STANDARD COVER"} or depending on what else might be in field2 you could get away with using the leading unique characters and a wildcard e.g. {SKIPIF {Mergefield field1} = "A"}{SKIPIF {Mergefield field2 \*Upper} = "DOWN*"}  Signature<>>< ><<> ><<> <>>< ><<> <>>< <>><<> Graham Mayor - Word MVP My web site www.gmayor.com Word MVP web site http://word.mvps.org <>>< ><<> ><<> <>>< ><<> <>>< <>><<> > Hello, > [quoted text clipped - 39 lines] >> This reply is posted in the Newsgroup; please post any follow >> question or reply in the newsgroup and not by e-mail :-) Graham, Thanks for your help. It must have been a data input issue instead, which is easier to solve! Thanks again. Regards, Chris > There is no reason why two SKIPIF statements immediately following one > another at the start of the letter should not work as you intend and worked [quoted text clipped - 51 lines] > >> This reply is posted in the Newsgroup; please post any follow > >> question or reply in the newsgroup and not by e-mail :-) FWIW, if you get this... 'Word could not parse the query into a valid SQL string' it's probably because you entered some filter criteria via the Mail merge Recipients/Query options dialog. When you use that dialog, Word sometimes does not generate SQL that the appropriate data provider can understand, and there are other problems with that approach as well. Peter Jamieson > Graham, > [quoted text clipped - 64 lines] >> >> This reply is posted in the Newsgroup; please post any follow >> >> question or reply in the newsgroup and not by e-mail :-)
|
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.