Runtime error 2147417851 80010105

Answers

• What version of office do you have installed on your PC?

  You can specify the version of excel you are creating the object.

  From :

  Set WordObj = CreateObject(«Word.Application»)

  to :

  Set WordObj = CreateObject(«Word.Application.12»)

  You also may want to try using the following

  WordObj.ActiveDocument.SaveAs FileName:=FullDocName, FileFormat:=acFileFormatAccess2007

  Check the menu in access vba Tools — References Microsoft Word XX.X object Library.  You may have to browse for a newer version of the object library.  what sometimes hapPens if the macro was developed on a PC with 2003 the reference may be
  pointing to the object library 11.0 while you need 12.0.

  Make sure the version  of the object library is compatible with Word 2007.  Version 12 is office 2007.  The create object will automatically use the defualt version of office that is installed on your PC.  If you have  office 2010
  installed you may need to specify a differnt version.

  Errors like -2147417851 (80010105) are usually caused by not having the priveledge to open the file.  Make sure you can open the file by double clicking on the file and opening.  I would aslo suspect you would get the error if your configuration
  (like the reference) doesn’t support office 2007.

  ---

  jdweng

  • Marked as answer by

    Friday, February 25, 2011 9:50 AM

• Wrong approach. You mix the application object with document object. Try this:

    Dim appWord As New Word.Application
    Dim objWord As Word.Document

    Set objWord = appWord.Documents.Add(GetTemplatePath(strDocPath))

    appWord.visible = True
    appWord.Activate
    appWord.ShowMe
    appWord.WindowState = wdWindowStateMaximize

    appWord.ActiveDocument.SaveAs FileName:=FullDocName, FileFormat:=12

  Greg

  • Marked as answer by
    Bruce Song
    Friday, February 25, 2011 9:50 AM

• Hi Richard,

  it’s interesting because this cide works fine for me with Office 2007:

   Set wordobj = CreateObject("Word.Application")
   wordobj.Visible = True
   wordobj.Activate
   wordobj.ShowMe
   wordobj.WindowState = wdWindowStateMaximize
   wordobj.Documents.Add "********Desktoptest.docx"
   wordobj.ActiveDocument.SaveAs FileName:="********Desktoptest1", FileFormat:=12
   wordobj.Quit
   Set wordobj = Nothing
  

  But I’ve been facinf the situation when Excel automation hadn’t worked until setting the whole object «stairway».

  Suggestions:

  — Are you sure that exactly the last line causes an error?

  — Does FullDocName have an extension part?

  — Do you have more than one version of Office installed on this workstation?

  ---

  Andrey V Artemyev | Saint-Petersburg, Russia

  • Marked as answer by
    Bruce Song
    Friday, February 25, 2011 9:50 AM

Hello Forum!

When I am running this code on a Windows XP platform whit Outlook2010 and Access2010 the code are working,
when I am running the same code on a Windows10 platform with Outlook2010 and Access2010 the code are NOT working, it stops at
.To = Me.Emailkontaktperson

and gives this message » Run-time error ‘ 2147417851 (80010105) Method’To’ of object’_MailItem’failed «

Do Forum have any suggestion to what are causing this???

Private Sub Kommandoknap35_Click()
Dim DocName As String
Dim objOutlook As Object
Dim objOutLookMsg As Object
Dim strBody As String
Dim DocPath As String
Dim rst As DAO.Recordset

‘Me.txtBillingEmail is a text field on the invoice form that has the billing email
‘On Error GoTo Kommandoknap35_Click_Error

If Me.Emailkontaktperson = «No billing email on file.» Then
‘When a customer has no email the system inserts the text
‘»No billing email on file.»
MsgBox «No billing email on file.», vbInformation, «Can’t Email»
Exit Sub
End If

‘The DocName is the name of the invoice report
DocName = «RapTilbud»
‘First, we open the report to the screen using the invoice #
DoCmd.OpenReport «RapTilbud», acViewPreview, , «[Ordrenr]=» & Me.Ordrenr

‘DocPath stores the complete path of the PDF
‘DocPath = CurrentProject.path & «Fakturanr» & » » & Me.Ordrenr & » » & Me.Kundenavn & » .pdf»
DocPath = «C:UsersCarstenDesktopTilbud2doo» & «Tilbud nr» & » » & Me.Ordrenr & » » & Me.Kundenavn & «.pdf»

‘Delete pdf if it exists
If Dir(DocPath) <> «» Then
Kill DocPath
End If

‘Second, we save the invoice to the directory where the program is launched from
‘we use the invoice number in the name of the file
‘DoCmd.OutputTo acOutputReport, DocName, acFormatPDF, CurrentProject.path & «Fakturanr» & » » & Me.Ordrenr & » » & Me.Kundenavn & » .pdf», False
DoCmd.OutputTo acOutputReport, DocName, acFormatPDF, «C:UsersCarstenDesktopTilbud2doo» & «Tilbud nr» & » » & Me.Ordrenr & » » & Me.Kundenavn & «.pdf», False
‘Close the report since it’s no longer needed
DoCmd.Close acReport, DocName

‘rst is opened to the options table that holds the subject and body templates
Set rst = CurrentDb.OpenRecordset(«Select * from Masterdata»)
‘objOutlook will be used to refence Outlook in the program
‘I recommend Outlook is open while the code is executing
Set objOutlook = CreateObject(«Outlook.Application»)
‘Create a new message:
Set objOutLookMsg = objOutlook.CreateItem(0)
With objOutLookMsg
‘Use the email field on the invoice for the To field
.To = Me.Emailkontaktperson
‘Optional: copy another email address that will receive a copy of the pdf
‘.CC = «any@what_ever.com”»

I had a similar problem, and it bugged the heck out of me. My eventual fix (workaround) was using a variable, which you wouldn’t think would matter. Declare a string variable and then populate and use it.

Dim strEmail As String
…
strEmail = Me.Emailkontaktperson
.To = strEmail

Originally Posted by pbaldy

I had a similar problem, and it bugged the heck out of me. My eventual fix (workaround) was using a variable, which you wouldn’t think would matter. Declare a string variable and then populate and use it.

Dim strEmail As String
…
strEmail = Me.Emailkontaktperson
.To = strEmail

Resolved thank you very much!!!

Happy to help and welcome to the site by the way! I stumped some great minds with that before stumbling on the answer while experimenting.

Originally Posted by pbaldy

I had a similar problem, and it bugged the heck out of me. My eventual fix (workaround) was using a variable, which you wouldn’t think would matter. Declare a string variable and then populate and use it.

Dim strEmail As String
…
strEmail = Me.Emailkontaktperson
.To = strEmail

————————

I was having the same problem, your example work great for me, Thanks!

I’m glad it helped you! I never got a definitive answer. It was speculated that the newer OS versions were trying to pass the object itself rather than the value within the object, and declaring a variable forced the result to be the desired string. Once I got it solved (or more accurately worked around) I stopped researching.

OS was my speculation because the only users I had that experienced the problem were those that had been upgraded. I had a client that had the same issue: code that had been working fine suddenly having this error when users were upgraded to Win 10. It could certainly have been something else. In my case, once I sorted it out it was on to the next crisis, so I didn’t go back and try to isolate the culprit.