#1
|
||||
|
||||
MM persistent request for seperators
As much as I’m reluctant to admit it, I’ve recently migrated from Office 2003 to something less archaic. I’m fairly certain it’s 2016, but this new (to me) UI doesn’t appear to have a Help/About spot that would tell what version I’m working with.
Anyway…I have a simple Mail Merge document that takes in a .csv file from Excel and extracts data that feeds a check printer. After converting to .docx, this MM operation now stops and needs to know the field separator, and the record separator each time it’s run. Does anyone know if there’s a way for me to make my choices either the default for Word, or, better yet, the default for just that document? I appreciate any input you might provide. Thanks. JLOB |
#2
|
||||
|
||||
Are you saving the mailmerge main document after connecting to the data source and defining the separators?
__________________
Cheers, Paul Edstein [Fmr MS MVP - Word] |
#3
|
||||
|
||||
Quote:
I’m not at all certain that I did it before, and only reasonably certain that I did that today. I certainly tried, but as yet, no joy. Part of the problem is that I built this routine in 2005 when I was, not only younger but infinitely more alert. I have two MM routines, this one and Christmas Card addressing. SHMBO (She who must be obeyed) opted to hand-address the cards this year, so I’m not sure if that one works anymore or not. I’ll worry about that one in November. I no longer remember how to change the source data, but I apparently did it correctly today. I don’t know how to determine what my main document is, so the change was made by accident. Be nice to know how to do it on a regular basis. As far as the separators, I continue to get the prompts. I can live with it, of course, but would prefer to do it right. Speaking of which… I’m also getting the warning about allowing SQL code when I invoke the document. I notice that you dealt with that in another response recently, but I believe that dealt with VBA macros, and my problem is a bit different. I’d really like to get rid of that warning. Thoughts? I’ve attached some screen shots. Thank you. JLOB |
#4
|
||||
|
||||
Quote:
Quote:
Microsoft introduced that some years ago, to warn users against running documents containing possibly malicious SQL code. If you answer 'No' to the prompt, the document disconnects from the data source. There is a registry edit for suppressing the warning.
__________________
Cheers, Paul Edstein [Fmr MS MVP - Word] |
#5
|
||||
|
||||
Quote:
Quote:
Quote:
Thanks for your continued help. On another note, I hope the fires near you aren't adversely affecting you or your family. JLOB |
#6
|
||||
|
||||
Quote:
See: https://support.microsoft.com/en-my/...command-messag See also: How to stop a Microsoft Word warning concerning a SQL command when - Microsoft Community
__________________
Cheers, Paul Edstein [Fmr MS MVP - Word] |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Hyperlink request | dbalaam | Word | 2 | 12-23-2017 04:54 AM |
"Ignore All" Not Persistent After Close and Reopen | retexan599 | Word | 7 | 10-30-2017 11:23 AM |
Review > Markup. Deselect "Formatting" is not persistent | OldGrantonian | Word | 3 | 02-06-2014 03:30 AM |
Formula Help Request | OTPM | Excel | 16 | 12-16-2013 01:57 PM |
Formula help request | JAMS | Excel | 2 | 04-06-2012 10:14 PM |