|
My guess is that the problem has to do with the 2010 installation. I have no
idea how to fix that. You might want to ask on the beta forum how to do a
complete uninstallation.
"Doug Robbins - Word MVP" <dkr@REMOVECAPSmvps.org> wrote in message
news:BB251675-C7E0-4172-A877-5AE61BFE3AA6@microsoft.com...
idea how to fix that. You might want to ask on the beta forum how to do a
complete uninstallation.
Sue Mosher, Outlook MVP
Author of Microsoft Outlook 2007 Programming:
Jumpstart for Power Users and Administrators
http://www.outlookcode.com/article.aspx?id=54
Author of Microsoft Outlook 2007 Programming:
Jumpstart for Power Users and Administrators
http://www.outlookcode.com/article.aspx?id=54
"Doug Robbins - Word MVP" <dkr@REMOVECAPSmvps.org> wrote in message
news:BB251675-C7E0-4172-A877-5AE61BFE3AA6@microsoft.com...
> Hi Sue,
>
> If I insert
>
> MsgBox ActiveDocument.MailEnvelope
>
> into the code, or just create a macro in the normal.dot template that
> contains that code, in both cases, I get the Run-Time error '430' message
>
> Class does not support Automation or does not support expected interface.
>
> The same error message appears if I try and run the following code from
> the VBA Help File:
>
> ActiveDocument.MailEnvelope.Introduction = _
> "Please review this document and let me know " & _
> "what you think. I need your input by Friday." & _
> " Thanks."
>
> I have tried deleting Registry Keys, and re-registering Word, but that did
> not make any difference
>
> I have also tried running the code from
> http://www.outlookcode.com/codedetail.aspx?id=1333 from Outlook, which did
> not work and if I comment out the On Error Resume Next, I get the same
> error message.
>
> BTW, this was a fresh install of Office 2003 on a machine that previously
> had 2010 Beta on it, but that was uninstalled before 2003 was installed
> and the Registry Keys for Office 14.0 have been deleted.
>
> --
> Regards,
>
> Doug Robbins - Word MVP
>
>
> "Sue Mosher [MVP]" <suemvp@gmail.com> wrote in message
> news:%23mu0mwarKHA.3792@TK2MSFTNGP05.phx.gbl...
>
> If I insert
>
> MsgBox ActiveDocument.MailEnvelope
>
> into the code, or just create a macro in the normal.dot template that
> contains that code, in both cases, I get the Run-Time error '430' message
>
> Class does not support Automation or does not support expected interface.
>
> The same error message appears if I try and run the following code from
> the VBA Help File:
>
> ActiveDocument.MailEnvelope.Introduction = _
> "Please review this document and let me know " & _
> "what you think. I need your input by Friday." & _
> " Thanks."
>
> I have tried deleting Registry Keys, and re-registering Word, but that did
> not make any difference
>
> I have also tried running the code from
> http://www.outlookcode.com/codedetail.aspx?id=1333 from Outlook, which did
> not work and if I comment out the On Error Resume Next, I get the same
> error message.
>
> BTW, this was a fresh install of Office 2003 on a machine that previously
> had 2010 Beta on it, but that was uninstalled before 2003 was installed
> and the Registry Keys for Office 14.0 have been deleted.
>
> --
> Regards,
>
> Doug Robbins - Word MVP
>
>
> "Sue Mosher [MVP]" <suemvp@gmail.com> wrote in message
> news:%23mu0mwarKHA.3792@TK2MSFTNGP05.phx.gbl...
>> What does ActiveDocument.MailEnvelope return?
>>
>> "Doug Robbins - Word MVP" <dkr@REMOVECAPSmvps.org> wrote in message
>> news:OBxY0jTrKHA.3800@TK2MSFTNGP06.phx.gbl...
>>
>>>
>> "Doug Robbins - Word MVP" <dkr@REMOVECAPSmvps.org> wrote in message
>> news:OBxY0jTrKHA.3800@TK2MSFTNGP06.phx.gbl...
>>> Hi Sue,
>>>
>>> Yes, it is being run from Word. It is in the Word 2003 version of the
>>> add-in that can be downloaded from:
>>>
>>> http://www.gmayor.com/ManyToOne.htm
>>>
>>> However, in the 2003 version that is available there, the "Merge to
>>> Email Message" facility has been disabled.
>>>
>>> The error is being caused by the
>>>
>>> Set objDoc = .MailEnvelope.Item
>>>
>>> command. Note that line of code is inside a With ActiveDocument...End
>>> With construction, and when writing the code, the intellisense provides
>>> MailEnvelope.Item as a suggestion.
>>>
>>> --
>>> Regards,
>>>
>>> Doug Robbins - Word MVP, originally posted via msnews.microsoft.com
>>>
>>> "Sue Mosher [MVP]" <suemvp@gmail.com> wrote in message
>>> news:u7E2jHTrKHA.728@TK2MSFTNGP04.phx.gbl...
>>>>>
>>> Yes, it is being run from Word. It is in the Word 2003 version of the
>>> add-in that can be downloaded from:
>>>
>>> http://www.gmayor.com/ManyToOne.htm
>>>
>>> However, in the 2003 version that is available there, the "Merge to
>>> Email Message" facility has been disabled.
>>>
>>> The error is being caused by the
>>>
>>> Set objDoc = .MailEnvelope.Item
>>>
>>> command. Note that line of code is inside a With ActiveDocument...End
>>> With construction, and when writing the code, the intellisense provides
>>> MailEnvelope.Item as a suggestion.
>>>
>>> --
>>> Regards,
>>>
>>> Doug Robbins - Word MVP, originally posted via msnews.microsoft.com
>>>
>>> "Sue Mosher [MVP]" <suemvp@gmail.com> wrote in message
>>> news:u7E2jHTrKHA.728@TK2MSFTNGP04.phx.gbl...
>>>> Which statement raises that error? You're running this code in Word
>>>> VBA?
>>>>
>>>> "Doug Robbins - Word MVP" <dkr@REMOVECAPSmvps.org> wrote in message
>>>> news:ef5ottSrKHA.5896@TK2MSFTNGP04.phx.gbl...
>>>>
>>>> VBA?
>>>>
>>>> "Doug Robbins - Word MVP" <dkr@REMOVECAPSmvps.org> wrote in message
>>>> news:ef5ottSrKHA.5896@TK2MSFTNGP04.phx.gbl...
>>>>> As a followup, if I remove the On Error Resume Next, the following
>>>>> error message is displayed:
>>>>>
>>>>> 430 Class does not support Automation or does not support expected
>>>>> interface
>>>>>
>>>>>>>>> error message is displayed:
>>>>>
>>>>> 430 Class does not support Automation or does not support expected
>>>>> interface
>>>>>
>>>>>> Based on Sue Mosher's code at
>>>>>> http://www.outlookcode.com/codedetail.aspx?id=1333, the following
>>>>>> code, which is located inside a With ActiveDocument - End With
>>>>>> construction, works fine in Word 2007:
>>>>>>
>>>>>> Set objDoc = .MailEnvelope.Item
>>>>>> With objDoc
>>>>>> .To = strEmail
>>>>>> .Subject = strSubject
>>>>>> .Save
>>>>>> strID = .EntryID
>>>>>> End With
>>>>>> Set objDoc = Nothing
>>>>>> Set objDoc =
>>>>>> oOutlookApp.Session.GetItemFromID(strID)
>>>>>> With objDoc
>>>>>> .Send
>>>>>> End With
>>>>>> Set objDoc = Nothing
>>>>>>
>>>>>> ObjDoc is declared as an Object and strID as a String and earlier in
>>>>>> the code there is the following:
>>>>>>
>>>>>> On Error Resume Next
>>>>>> Set oOutlookApp = GetObject(, "Outlook.Application")
>>>>>> If Err <> 0 Then
>>>>>> Set oOutlookApp = CreateObject("Outlook.Application")
>>>>>> bStarted = True
>>>>>> End If
>>>>>>
>>>>>> In Word 2003 however, it does not work and testing for strID using
>>>>>> MsgBox strID after it is set to .EntryID, I just get an empty message
>>>>>> box so that it appears that .EntryID is not being assigned.
>>>>>>
>>>>>> Any clues on how to overcome this?
>>>>>>>>>>> http://www.outlookcode.com/codedetail.aspx?id=1333, the following
>>>>>> code, which is located inside a With ActiveDocument - End With
>>>>>> construction, works fine in Word 2007:
>>>>>>
>>>>>> Set objDoc = .MailEnvelope.Item
>>>>>> With objDoc
>>>>>> .To = strEmail
>>>>>> .Subject = strSubject
>>>>>> .Save
>>>>>> strID = .EntryID
>>>>>> End With
>>>>>> Set objDoc = Nothing
>>>>>> Set objDoc =
>>>>>> oOutlookApp.Session.GetItemFromID(strID)
>>>>>> With objDoc
>>>>>> .Send
>>>>>> End With
>>>>>> Set objDoc = Nothing
>>>>>>
>>>>>> ObjDoc is declared as an Object and strID as a String and earlier in
>>>>>> the code there is the following:
>>>>>>
>>>>>> On Error Resume Next
>>>>>> Set oOutlookApp = GetObject(, "Outlook.Application")
>>>>>> If Err <> 0 Then
>>>>>> Set oOutlookApp = CreateObject("Outlook.Application")
>>>>>> bStarted = True
>>>>>> End If
>>>>>>
>>>>>> In Word 2003 however, it does not work and testing for strID using
>>>>>> MsgBox strID after it is set to .EntryID, I just get an empty message
>>>>>> box so that it appears that .EntryID is not being assigned.
>>>>>>
>>>>>> Any clues on how to overcome this?
>>>>
>>
| 13 Feb 2010 | Using VBA to send Word document as body of message works in 2007, but not in ... | .Doug Robbins - Word MVP |
| 14 Feb 2010 |  Re: Using VBA to send Word document as body of message works in 2007, but not... | .Doug Robbins - Word MVP |
| 14 Feb 2010 |  Re: Using VBA to send Word document as body of message works in 2007, but not... | .Sue Mosher [MVP] |
Contact Us
All times are in (US) Eastern Daylight Time (GMT -4:00)
All times are in (US) Eastern Daylight Time (GMT -4:00)