Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
DiscussionsAccessExcelInfoPathOutlookPowerPointPublisherWord
DirectoryUser Groups
Related Topics
Outlook ExpressInternet ExplorerWindowsMS Server ProductsMore Topics ...

MS Office Forum / Word / Mailmerge and Fax / May 2006

Tip: Looking for answers? Try searching our database.

Access to word Mail merge problem: Requested object is not available

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
mbbostwick@gmail.com - 09 May 2006 12:22 GMT
I have a problem with a mail merge procedure I used to use with Access
'97.

We recently converted to Office XP (2002) and I now have an issue I am
unfamilliar with and have been unable to resolve.

I am trying to merge individual records into seperate mail merge word
docs.  In the past I linked my word files directly to the tables and
then simply changed the QueryString of the merge file for the
particular record I need to create a file for.

Here is a sample of the code I used in the past.

*******************************************************************
Private Sub Command0_Click()

   Dim w As Word.Application
   Dim m As MailMerge
   Dim mm As MailMergeDataSource
   Dim d As Word.Document
   Dim rst1 As dao.Recordset

   Set rst1 = CurrentDb.OpenRecordset("tblMergeData")

   Do Until rst1.EOF
       Set w = New Word.Application
       w.Visible = True
       Set d = w.Documents.Open("H:\My Documents\MyLetter.doc")
       Set m = d.MailMerge
       Set mm = d.MailMerge.DataSource

       'I Get the error
       '[ Run Time Error '5852':
       'Requested object is not available ]
       'on the next line.  This code was not a problem in Office '97

       mm.QueryString = "SELECT * FROM tblMergeData WHERE MergeF1 = '"
& rst1!myfield & "'"

       m.Execute
       Set mm = Nothing
       Set m = Nothing
       d.Close wdDoNotSaveChanges
       Set d = w.Documents("Form Letters1")
       d.SaveAs ("H:\My Documents\MyLetter" & rst1!Myfield1 & ".doc")
       d.Close
       w.Quit
       Set w = Nothing
       rst1.MoveNext
   Loop

End Sub

***************************************************************

Please note, I do realise I could change the source of my mail merge
file to a query and just change the SQL of my Query, however I have
several documents that use this method and would like to preserve the
process if at all possible.

I appreciate any thoughts.

Mike

This has been cross posted from: comp.databases.ms-access
Doug Robbins - Word MVP - 09 May 2006 19:13 GMT
I assume from your code that you are manually attaching the datasource to
the mailmerge main document.

That being the case, from the Tools menu in Word, select Options and then go
to the General tab and check the box against "Confirm conversions at open."
After you do this, when you attach the data source to the mail merge main
document, you will be given a number of options for the method by which the
connection should be made.  Selecting the DDE option will probably overcome
your
problem.

Signature

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

>I have a problem with a mail merge procedure I used to use with Access
> '97.
[quoted text clipped - 61 lines]
>
> This has been cross posted from: comp.databases.ms-access
Peter Jamieson - 10 May 2006 11:22 GMT
In this case, you probably need to read the following knowledgebase article
even though the title may not seem related to your problem.

"Opening This Will Run the Following SQL Command" Message When You Open a
Word
Document - 825765
http://support.microsoft.com?kbid=825765

Peter Jamieson
>I have a problem with a mail merge procedure I used to use with Access
> '97.
[quoted text clipped - 61 lines]
>
> This has been cross posted from: comp.databases.ms-access
 
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.