Custom form created in 2003 won't print since upgrade to 2007

[TG9yaV9DQg]

We created multiple Outlook forms that print to Word templates via code in a

Print button. The forms were created in 2003. We recently upgraded to 2007.

Now, when we click the button, the Word template prints but it doesn't

contain the information from the form.

Any ideas?

 

[Sue Mosher [MVP]]

Code in a print button on the form or in Word? You may want to add MsgBox

statements to the code to help you see how it's branching and executing.

Sue Mosher

"Lori_CB" <Lori_CB> wrote in message

news:722B9CAD-754D-435D-B2DB-3960654B6CD6@microsoft.com...
> We created multiple Outlook forms that print to Word templates via code in
> a
> Print button. The forms were created in 2003. We recently upgraded to
> 2007.
> Now, when we click the button, the Word template prints but it doesn't
> contain the information from the form.

> Any ideas?

 

[TG9yaV9DQg]

The code is for the Print button on the Outlook form. It's used to open

Word, populate the Word fields, print the document and close Word.

"Sue Mosher [MVP]" wrote:


> Code in a print button on the form or in Word? You may want to add MsgBox
> statements to the code to help you see how it's branching and executing.
> > Sue Mosher
> > >

> "Lori_CB" <Lori_CB> wrote in message
> news:722B9CAD-754D-435D-B2DB-3960654B6CD6@microsoft.com...
> > We created multiple Outlook forms that print to Word templates via code in
> > a
> > Print button. The forms were created in 2003. We recently upgraded to
> > 2007.
> > Now, when we click the button, the Word template prints but it doesn't
> > contain the information from the form.
> > Any ideas?

>

 

[Sue Mosher [MVP]]

Did you try what I suggested? Or run the code in the script debugger?

Sue Mosher

"Lori_CB" <LoriCB> wrote in message

news:203C0444-F9F5-41E6-A3BC-917081E88651@microsoft.com...
> The code is for the Print button on the Outlook form. It's used to open
> Word, populate the Word fields, print the document and close Word.

> "Sue Mosher [MVP]" wrote:
>
> > Code in a print button on the form or in Word? You may want to add MsgBox
> > statements to the code to help you see how it's branching and executing.
>

>> "Lori_CB" <Lori_CB> wrote in message
> > news:722B9CAD-754D-435D-B2DB-3960654B6CD6@microsoft.com...
> > > We created multiple Outlook forms that print to Word templates via code
> > > in
> > > a
> > > Print button. The forms were created in 2003. We recently upgraded to
> > > 2007.
> > > Now, when we click the button, the Word template prints but it doesn't
> > > contain the information from the form.
> >> > Any ideas?
>

>
>>

 

[TG9yaV9DQg]

I tried the msgbox and the fields are getting filled in properly.

When I try to use the Script Debugger, it says the feature is not available

and to run setup again. I'm waiting for a reply from our Help Desk.

"Sue Mosher [MVP]" wrote:


> Did you try what I suggested? Or run the code in the script debugger?
> > Sue Mosher
> > >

> "Lori_CB" <LoriCB> wrote in message
> news:203C0444-F9F5-41E6-A3BC-917081E88651@microsoft.com...
> > The code is for the Print button on the Outlook form. It's used to open
> > Word, populate the Word fields, print the document and close Word.
> > "Sue Mosher [MVP]" wrote:
> >
> >> Code in a print button on the form or in Word? You may want to add MsgBox
> >> statements to the code to help you see how it's branching and executing.
> >
> >> "Lori_CB" <Lori_CB> wrote in message
> >> news:722B9CAD-754D-435D-B2DB-3960654B6CD6@microsoft.com...
> >> > We created multiple Outlook forms that print to Word templates via code
> >> > in
> >> > a
> >> > Print button. The forms were created in 2003. We recently upgraded to
> >> > 2007.
> >> > Now, when we click the button, the Word template prints but it doesn't
> >> > contain the information from the form.
> >> >> > Any ideas?
> >
> >
> >>

>

 

[Sue Mosher [MVP]]

Script debugger is an optional component that may not have been installed;

it definitely won't work on Vista unless you also have Visual Studio.

That's why I suggested using MsgBox statements.

What do you mean by "the fields are getting filled in properly" -- the

fields in the Outlook item or the fields in the Word document? What happens

if you change the code so that the Word document displays instead of being

printed?

Sue Mosher

"Lori_CB" <LoriCB> wrote in message

news:255A6EC0-494E-42BE-BA8E-DA73C0556BE2@microsoft.com...
> I tried the msgbox and the fields are getting filled in properly.

> When I try to use the Script Debugger, it says the feature is not
> available
> and to run setup again. I'm waiting for a reply from our Help Desk.

> "Sue Mosher [MVP]" wrote:
>
> > Did you try what I suggested? Or run the code in the script debugger?
>

>> "Lori_CB" <LoriCB> wrote in message
> > news:203C0444-F9F5-41E6-A3BC-917081E88651@microsoft.com...
> > > The code is for the Print button on the Outlook form. It's used to
> > > open
> > > Word, populate the Word fields, print the document and close Word.
> >> > "Sue Mosher [MVP]" wrote:
> >> >> Code in a print button on the form or in Word? You may want to add
> > >> MsgBox
> > >> statements to the code to help you see how it's branching and
> > >> executing.
> > >
>> >> "Lori_CB" <Lori_CB> wrote in message
> > >> news:722B9CAD-754D-435D-B2DB-3960654B6CD6@microsoft.com...
> > >> > We created multiple Outlook forms that print to Word templates via
> > >> > code
> > >> > in
> > >> > a
> > >> > Print button. The forms were created in 2003. We recently upgraded
> > >> > to
> > >> > 2007.
> > >> > Now, when we click the button, the Word template prints but it
> > >> > doesn't
> > >> > contain the information from the form.

 

[TG9yaV9DQg]

We have XP Professional, so I'm hoping to get it back. It's another thing

that stopped working after the upgrade. There must be something to tweak.

I did a message box for the Outlook field value and for the Word field

value. Both were correct.

I changed oDoc.PrintOut to oDoc.Display and got the following error message:

"Object doesn't support this property or method: 'oDoc.Display'"

Should I be changing something else too?

Thanks for all your help and patience.

"Sue Mosher [MVP]" wrote:


> Script debugger is an optional component that may not have been installed;
> it definitely won't work on Vista unless you also have Visual Studio.
> That's why I suggested using MsgBox statements.

> What do you mean by "the fields are getting filled in properly" -- the
> fields in the Outlook item or the fields in the Word document? What happens
> if you change the code so that the Word document displays instead of being
> printed?
> > Sue Mosher
> > >

> "Lori_CB" <LoriCB> wrote in message
> news:255A6EC0-494E-42BE-BA8E-DA73C0556BE2@microsoft.com...
> >I tried the msgbox and the fields are getting filled in properly.
> > When I try to use the Script Debugger, it says the feature is not
> > available
> > and to run setup again. I'm waiting for a reply from our Help Desk.
> > "Sue Mosher [MVP]" wrote:
> >
> >> Did you try what I suggested? Or run the code in the script debugger?
> >
> >> "Lori_CB" <LoriCB> wrote in message
> >> news:203C0444-F9F5-41E6-A3BC-917081E88651@microsoft.com...
> >> > The code is for the Print button on the Outlook form. It's used to
> >> > open
> >> > Word, populate the Word fields, print the document and close Word.
> >> >> > "Sue Mosher [MVP]" wrote:
> >> >> >> Code in a print button on the form or in Word? You may want to add
> >> >> MsgBox
> >> >> statements to the code to help you see how it's branching and
> >> >> executing.
> >> >
> >> >> "Lori_CB" <Lori_CB> wrote in message
> >> >> news:722B9CAD-754D-435D-B2DB-3960654B6CD6@microsoft.com...
> >> >> > We created multiple Outlook forms that print to Word templates via
> >> >> > code
> >> >> > in
> >> >> > a
> >> >> > Print button. The forms were created in 2003. We recently upgraded
> >> >> > to
> >> >> > 2007.
> >> >> > Now, when we click the button, the Word template prints but it
> >> >> > doesn't
> >> >> > contain the information from the form.

>

 

[Sue Mosher [MVP]]

The object browser (F2 in VBA) is your friend. If you look at the Document

object in the Word library, you'll see that it has no Display method, but it

does have an Activate method and Window.Visible property.

You might want to show enough of your code so we can see how you're creating

the document and printing it. Please DO NOT show all the code for filling

the fields; as you said, it's clear that's working.

Sue Mosher

"Lori_CB" <LoriCB> wrote in message

news:E86D1E0A-899C-45A0-9F97-5A6FC0E10842@microsoft.com...
> We have XP Professional, so I'm hoping to get it back. It's another thing
> that stopped working after the upgrade. There must be something to tweak.

> I did a message box for the Outlook field value and for the Word field
> value. Both were correct.

> I changed oDoc.PrintOut to oDoc.Display and got the following error
> message:
> "Object doesn't support this property or method: 'oDoc.Display'"

> Should I be changing something else too?

> Thanks for all your help and patience.

> "Sue Mosher [MVP]" wrote:
>
> > Script debugger is an optional component that may not have been
> > installed;
> > it definitely won't work on Vista unless you also have Visual Studio.
> > That's why I suggested using MsgBox statements.
>

>> What do you mean by "the fields are getting filled in properly" -- the
> > fields in the Outlook item or the fields in the Word document? What
> > happens
> > if you change the code so that the Word document displays instead of
> > being
> > printed?
> > > > Sue Mosher
> > >> >> >
>
>> "Lori_CB" <LoriCB> wrote in message
> > news:255A6EC0-494E-42BE-BA8E-DA73C0556BE2@microsoft.com...
> > >I tried the msgbox and the fields are getting filled in properly.
> >> > When I try to use the Script Debugger, it says the feature is not
> > > available
> > > and to run setup again. I'm waiting for a reply from our Help Desk.
> >> > "Sue Mosher [MVP]" wrote:
> >> >> Did you try what I suggested? Or run the code in the script debugger?
> > >
>> >> "Lori_CB" <LoriCB> wrote in message
> > >> news:203C0444-F9F5-41E6-A3BC-917081E88651@microsoft.com...
> > >> > The code is for the Print button on the Outlook form. It's used to
> > >> > open
> > >> > Word, populate the Word fields, print the document and close Word.
> > >>> >> > "Sue Mosher [MVP]" wrote:
> > >>> >> >> Code in a print button on the form or in Word? You may want to add
> > >> >> MsgBox
> > >> >> statements to the code to help you see how it's branching and
> > >> >> executing.
> > >> >
>> >> >> "Lori_CB" <Lori_CB> wrote in message
> > >> >> news:722B9CAD-754D-435D-B2DB-3960654B6CD6@microsoft.com...
> > >> >> > We created multiple Outlook forms that print to Word templates
> > >> >> > via
> > >> >> > code
> > >> >> > in
> > >> >> > a
> > >> >> > Print button. The forms were created in 2003. We recently
> > >> >> > upgraded
> > >> >> > to
> > >> >> > 2007.
> > >> >> > Now, when we click the button, the Word template prints but it
> > >> >> > doesn't
> > >> >> > contain the information from the form.
>

>
>>

 

[TG9yaV9DQg]

The code I've been referring to is in Outlook, not Word.

Here's what I'm doing when trying to display the Word document

(see <<< comments in the code):

Sub cmdPrint_Click()

Set oWordApp = CreateObject("Word.Application")

If oWordApp Is Nothing Then

MsgBox "Couldn't start Word."

Else

Dim oWordApp

Dim oWordDoc

Dim bolPrintBackground

' Open a new document

Set oDoc = oWordApp.Documents.Add

("\\w2kcbutler\data\eforms\pcrenewal2.dot")

' <<< deleted setting the field values

' Get the current Word setting for background printing

bolPrintBackground = oWordApp.Options.PrintBackground

' Turn background printing off

oWordApp.Options.PrintBackground = False

' Print the Word document

'oDoc.PrintOut <<< commented out

oDoc.Display <<< added

' Restore previous setting

oWordApp.Options.PrintBackground = bolPrintBackground

' Close and don't save changes to the document

'Const wdDoNotSaveChanges = 0 <<< commented out

'oDoc.Close wdDoNotSaveChanges <<< commented out

' Close the Word instance

'oWordApp.Quit <<< commented out

' Clean up

Set oDoc = Nothing

Set oWordApp = Nothing

End If

End Sub

 

[Sue Mosher [MVP]]

The code may be in Outlook, but you're using Word objects, so you need to

pay attention to what properties and methods those objects expose. Don't

assume you know what they are; look them up in the object browser.

Did you try using the Activate method I pointed out?

Sue Mosher

"Lori_CB" <LoriCB> wrote in message

news:5480F575-5F33-44F6-B206-B6258FD3C7EA@microsoft.com...
> The code I've been referring to is in Outlook, not Word.

> Here's what I'm doing when trying to display the Word document
> (see <<< comments in the code):
> Sub cmdPrint_Click()
> Set oWordApp = CreateObject("Word.Application")
> If oWordApp Is Nothing Then
> MsgBox "Couldn't start Word."
> Else
> Dim oWordApp
> Dim oWordDoc
> Dim bolPrintBackground

> ' Open a new document
> Set oDoc = oWordApp.Documents.Add
> ("\\w2kcbutler\data\eforms\pcrenewal2.dot")

> ' <<< deleted setting the field values

> ' Get the current Word setting for background printing
> bolPrintBackground = oWordApp.Options.PrintBackground

> ' Turn background printing off
> oWordApp.Options.PrintBackground = False

> ' Print the Word document
> 'oDoc.PrintOut <<< commented out
> oDoc.Display <<< added

> ' Restore previous setting
> oWordApp.Options.PrintBackground = bolPrintBackground

> ' Close and don't save changes to the document
> 'Const wdDoNotSaveChanges = 0 <<< commented out
> 'oDoc.Close wdDoNotSaveChanges <<< commented out

> ' Close the Word instance
> 'oWordApp.Quit <<< commented out

> ' Clean up
> Set oDoc = Nothing
> Set oWordApp = Nothing
> End If
> End Sub
>

 

[TG9yaV9DQg]

I tried the Activate and PrintPreview methods. Each time, nothing happened

when I clicked the Outlook Print button.

 

[Sue Mosher [MVP]]

You can also try adding a statement to set the document's

ActiveWindow.Visible property to True.

You might also want to comment out any On Error Resume Next statement so you

can get a better handle on any errors that may be occurring.

Sue Mosher

"Lori_CB" <LoriCB> wrote in message

news:A4D68340-3668-4417-909E-0FB0540BC86E@microsoft.com...

> I tried the Activate and PrintPreview methods. Each time, nothing
> happened
> when I clicked the Outlook Print button.
>

 

[TG9yaV9DQg]

You are a goddess!

The ActiveWindow.Visible property and PrintPreview let me see the

information is on the form.

I added some message boxes so I know the form was filled out before the

PrintPreview statement and then after the PrintPreview statement.

When it hit the PrintOut statement, it cleared the form then did the actual

print.

Here's the code I used to test it.

' Print the Word document

msgbox "before preview"

oDoc.PrintPreview

msgbox "after preview"

oDoc.PrintOut

msgbox "after printout"

Now, I know it's the PrintOut statement that's causing the problem.

This has been driving me crazy for a week....thank you for saving my sanity.

 

[Sue Mosher [MVP]]

Wow, that sounds quite odd, but at least you can print it manually once you

have it in preview. You might want to ask in a Word forum about why the form

fields are clearing.

Sue Mosher

"Lori_CB" <LoriCB> wrote in message

news:315C2FD7-1018-490B-A97A-998A00595E61@microsoft.com...

> You are a goddess!

> The ActiveWindow.Visible property and PrintPreview let me see the
> information is on the form.

> I added some message boxes so I know the form was filled out before the
> PrintPreview statement and then after the PrintPreview statement.

> When it hit the PrintOut statement, it cleared the form then did the
> actual
> print.

> Here's the code I used to test it.
> ' Print the Word document
> msgbox "before preview"
> oDoc.PrintPreview
> msgbox "after preview"
> oDoc.PrintOut
> msgbox "after printout"

> Now, I know it's the PrintOut statement that's causing the problem.

> This has been driving me crazy for a week....thank you for saving my
> sanity.