Sending Emails in Groupwise 7

[Stephen English]

I have been using this code to send emails in Groupwise 6.5 with no problems.
With Groupwise 7, it fails at the .subject line with message
"Run Time error '91'
Object variable or with block variable not set
It does not like .subject, .addrecipient and yet it brings them up when you
type a period

docActive.SaveAs strTemp
docActive.HasRoutingSlip = True
With docActive.RoutingSlip
.Subject = "Gifts and Benefits Declaration from " & Me.txtAuthor
.AddRecipient strEmail(i)
.Delivery = wdAllAtOnce
End With

Any ideas please?
Stephen

 

[Jean-Guy Marcil]

I have been using this code to send emails in Groupwise 6.5 with no problems.
With Groupwise 7, it fails at the .subject line with message
"Run Time error '91'
Object variable or with block variable not set
It does not like .subject, .addrecipient and yet it brings them up when you
type a period

docActive.SaveAs strTemp
docActive.HasRoutingSlip = True
With docActive.RoutingSlip
.Subject = "Gifts and Benefits Declaration from " & Me.txtAuthor
.AddRecipient strEmail(i)
.Delivery = wdAllAtOnce
End With

Any ideas please?

I do not know anything about Groupwise, so this is just an educated guess...

If your code did work with Groupwise 6.5, but does not with Groupwise 7, and
given that this is the only difference (You are still using the same OS and
Office versions, right?), then the problem is with Groupwise. The fact that
Word VBA Intellisense offers ".Subject" or ".AddRecipient" has nothing to do
with Groupwise. These Intellisense offers are from the Word object model, not
Groupwise.
It may be that the newest version of Groupwise has different internal
format/procedures, making the information it receives from Word through the
RoutingSlip method no longer compatible... Maybe it no longer likes receiving
variables and only accepts "real" strings...

 

[mcflyy]

Hey Stephen,

We have a state controled Novell system at my site. Earlier this year
they rolled out GW7 via NAL, and it too broke our ability to send Word
documents via Routing Recipient.

What I found that I had to do (granted this is specific to our setup,
but it may give you a starting point) was to uninstall GW7 via the
Windows Add/Remove Programs. Then I verified (or re-installed) GW7
and rebooted.

After the reboot, DO NOT open GW7. I found that I had to then
reinstall Windows Messaging (ver 4.0 at our site). After that
reinstall, I could open GW7, open Word, and use my forms that used
Routing Recipient.

Hope this is in some way helpful.