• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 753
  • Last Modified:

Documents.Add Does Not Return Document Object

We have a macro that creates a new document from a template and then "does stuff" with the resulting document. This used to work fine.

Today, without any apparent cause, the code throws an error. Stepping through the code, I can see that everything works fine, up until the point where I accept the returned object from Documents.Add into a Document variable and try to use that variable (see code). The document is created perfectly, the frmLetter form displays and is processed properly, and all the code in frmLetter runs without error. The end result is an open Letter document, processed like we expect Letter.dot to do.

It's only after the code returns from the call to Documents.Add that the weirdness starts. Apparently, the Documents.Add call does not return an object here.

Any ideas on what might cause this weird behaviour?
'Macro in standard module:
Public Sub CreateLetter()
   Dim doc As Word.Document
   Set doc = Application.Documents.Add(strWorkgroup & "Letter.dot")
   ' "Do stuff" with the resulting document:
   Call MsgBox(doc.Name) '--> RTE: Object variable or with block variable not Set
                         '    and stepping through the code, I can see that
                         '    the doc variable is indeed Nothing
End Sub
 
'Event in Letter.dot:
Private Sub Document_New()
   Dim f As frmLetter
   Set f = New frmLetter
   With f
      Set .CurrentDocument = ActiveDocument
      .Show
      'After cmdOK_Click, frmLetter processes its CurrentDocument correctly
   End With
   Set f = Nothing
End Sub

Open in new window

0
FlorisMK
Asked:
FlorisMK
1 Solution
 
FlorisMKAuthor Commented:
Solved:

One of the things that cmdOK_Click does is open, read, and close our central repository template (which contains our house style Styles and AutoText entries). Apparently, opening another document from within the Documents.Add runtime scope breaks the reference to the newly created document.

Working with ActiveDocument instead of using the return object from Add solves the issue. I don't like the solution, because with taskbar buttons and fidgety users you can't always rely on ActiveDocument, but it's the best I can do in this situation.

Edited the code to read:


'Macro in standard module:
Public Sub CreateLetter()
   Dim doc As Word.Document
   Call Application.Documents.Add(strWorkgroup & "Letter.dot")
   ' "Do stuff" with the resulting document:
   Set doc = ActiveDocument
   Call MsgBox(doc.Name) '--> NO RTE, Doc is set
End Sub

Open in new window

0

Featured Post

Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now