Word mailmerge - Visual Basic experts please help!

I would suggest that you take a look at the information provided in the
following post by fellow MVP Albert Kallal:

Actually, use my merge sample. it don't give that warning, and you don't
have to change registiry stuff etc.

The sample I have can be found here:
http://www.members.shaw.ca/AlbertKallal/msaccess/msaccess.html

What is nice/interesting about my sample is that is specially designed to
enable ANY form with ONE LINE of code....

Thus, each time you build a new form, you can word merge enable it with
great ease.

Make sure you read the instructions from above, and you should eventually
get to the follwoing page
http://www.members.shaw.ca/AlbertKallal/wordmerge/page2.html


Note that the merge can also use a query, and thus you don't have to merge
just "one" record..

After the merge occurs, you get a plain document WITHOUT any merge fields,
and this allows the end user to save, edit, or even email the document
(since the merge fields are gone after the merge occurs).

Give the above a try.


--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal.DeleteThis@msn.com


--
Hope this helps.

Please reply to the newsgroup unless you wish to avail yourself of my
services on a paid consulting basis.

Doug Robbins - Word MVP

"Murray Muspratt-Rouse" <Murray.Muspratt-Rouse.2ff6e68.DeleteThis@wordbanter.com> wrote
in message news:Murray.Muspratt-Rouse.2ff6e68@wordbanter.com...
>
> Doug, below you will find what I wrote in post no 25. After you had
> queried why I had commented out some code I cleaned up what I ran and
> tried again. I have copied in the code I used as well. In your latest
> post you have omitted the 'End Sub' - is that significant? I have
> checked my code against what you recommended and can find no difference
> - I am sure you must be correct!
>
> "The reason I commented out all the other lines of code was so as to
> make it easier to get back to where I was if the recommendations did
> not succeed in solving the problem. I will back up the database and do
> it again, removing all the code not included in your recommendations.
> Then, if it fails again, I will be able to restore the module from the
> backup.
>
> I have done as I said I would above, with the same result. Here is the
> code that ran."
>
> Sub OpenWordDoc(strDocName As String, strLetterDescription As String,
> strFormName As String)
> Dim objApp As Object
> Dim objMMMD As Object
> Dim strCurrentFileName As String
> On Error Resume Next
> DoCmd.OpenQuery "qrydeleteMergeTablerows"
>
>
> 'Load data to MergeTable with a query that collects the required data
> after update
>
> If strFormName = "Volunteers" Then
> If strLetterDescription = "REFERENCE REQUEST" Then
> DoCmd.OpenQuery ("qryUpdateRefereeLetterDate")
> DoCmd.OpenQuery ("qryReferees")
> Else
> If strLetterDescription = "Referee chaser" Then
> DoCmd.OpenQuery ("qryUpdateRefereeChaserDate")
> DoCmd.OpenQuery ("qryRefereechaser")
> Else
> DoCmd.OpenQuery ("qryVolunteer")
> End If
> End If
> Else
> DoCmd.OpenQuery ("qryClient")
> End If
>
> strCurrentFileName = CurrentDb.Name
>
> Set objApp = CreateObject("Word.Application")
> objApp.Activate
> Set objMMMD = objApp.Documents.Open(FileName:=strDocName)
>
> With objMMMD
> MailMerge.OpenDataSource Name:= _
> strCurrentFileName, _
> ConfirmConversions:=False, ReadOnly:=False, LinkToSource:=True, _
> AddToRecentFiles:=False, PasswordDocument:="", PasswordTemplate:="", _
> WritePasswordDocument:="", WritePasswordTemplate:="", Revert:=False, _
> Connection:= _
> "Provider=Microsoft.Jet.OLEDB.4.0;Password="""";Us er ID=Admin;Date
> Source=strCurrentFileName;Mode=Read;Extended Properties="""";Jet
> OLEDB:System database="""";Jet OLEDB:Registry Path="""";Jet
> OLEDBatabase Password="""";Jet OLE" _
> , SQLStatement:="SELECT * FROM `mergetable`", SQLStatement1:="", _
> SubType:=wdMergeSubTypeAccess
> Destination = wdSendToNewDocument
> SuppressBlankLines = True
> With .DataSource
> FirstRecord = .ActiveRecord
> LastRecord = .ActiveRecord
> End With
> Execute Pause:=False
> Close wdDoNotSaveChanges
> End With
>
> End Sub
>
>
> Doug Robbins - Word MVP;361443 Wrote:
>> There are some significant differences in this section of the code in
>> your
>> message from that which I provided, that would cause it not to compile
>>
>> correctly:
>>
>> Set objApp = CreateObject("Word.Application")
>> 'objApp.Visible = False
>> objApp.Activate
>> 'Dim objMMMD As Object
>> Set objMMMD = objApp.Documents.Open(FileName:=strDocName)
>>
>> 'objApp.Documents.Open FileName:=strDocName,
>> ConfirmConversions:=False, _
>> 'ReadOnly:=False, AddToRecentFiles:=False _
>> ', PasswordDocument:="", _
>> 'PasswordTemplate:="", Revert:=False,
>> WritePasswordDocument:="", _
>> 'WritePasswordTemplate:="", XMLTransform:=""
>>
>> 'objApp.ActiveDocument.MailMerge.OpenDataSource Name:= _
>>
>> With objMMMD
>> MailMerge.OpenDataSource Name:=strCurrentFileName, _
>> ConfirmConversions:=False, ReadOnly:=False, LinkToSource:=True,
>> _
>> AddToRecentFiles:=False, PasswordDocument:="",
>> PasswordTemplate:="", _
>> WritePasswordDocument:="", WritePasswordTemplate:="",
>> Revert:=False, _
>> Connection:= _
>> "Provider=Microsoft.Jet.OLEDB.4.0;Password="""";User
>> ID=Admin;Date Source=strCurrentFileName;Mode=Read;Extended
>> Properties="""";Jet OLEDB:System database="""";Jet OLEDB:Registry
>> Path="""";Jet OLEDB:Database Password="""";Jet OLE" _
>> , SQLStatement:="SELECT * FROM `mergetable`",
>> SQLStatement1:="", _
>> SubType:=wdMergeSubTypeAccess
>> Destination = wdSendToNewDocument
>> SuppressBlankLines = True
>> With .DataSource
>> FirstRecord = .ActiveRecord
>> LastRecord = .ActiveRecord
>> End With
>> Execute Pause:=False
>> Close wdDoNotSaveChanges
>> End With
>>
>>
>> --
>> Hope this helps.
>>
>> Please reply to the newsgroup unless you wish to avail yourself of my
>> services on a paid consulting basis.
>>
>> Doug Robbins - Word MVP
>>
>>
>
>
> +-------------------------------------------------------------------+
> +-------------------------------------------------------------------+
>
>
>
> --
> Murray Muspratt-Rouse

Thank you, Doug, for referring me to Albert Kallal's posts. I have
decided to 'leave well alone', and persuade the users that being able
to make changes to the merge document, and to the results of the merge,
is exactly what they need!

Murray

Doug Robbins - Word MVP;361660 Wrote:
> I would suggest that you take a look at the information provided in the
>
> following post by fellow MVP Albert Kallal:
>
> Actually, use my merge sample. it don't give that warning, and you
> don't
> have to change registiry stuff etc.
>
> The sample I have can be found he
> http://www.members.shaw.ca/AlbertKallal/msaccess/msaccess.html
>
> What is nice/interesting about my sample is that is specially designed
> to
> enable ANY form with ONE LINE of code....
>
> Thus, each time you build a new form, you can word merge enable it
> with
> great ease.
>
> Make sure you read the instructions from above, and you should
> eventually
> get to the follwoing page
> http://www.members.shaw.ca/AlbertKallal/wordmerge/page2.html
>
>
> Note that the merge can also use a query, and thus you don't have to
> merge
> just "one" record..
>
> After the merge occurs, you get a plain document WITHOUT any merge
> fields,
> and this allows the end user to save, edit, or even email the document
> (since the merge fields are gone after the merge occurs).
>
> Give the above a try.
>
>
> --
> Albert D. Kallal (Access MVP)
> Edmonton, Alberta Canada
> pleaseNOOSpamKallal RemoveThis @msn.com
>
>
> --
> Hope this helps.
>
> Please reply to the newsgroup unless you wish to avail yourself of my
> services on a paid consulting basis.
>
> Doug Robbins - Word MVP
>
>


+-------------------------------------------------------------------+
+-------------------------------------------------------------------+



--
Murray Muspratt-Rouse