MartyConnelly
martyconnelly at shaw.ca
Fri Jan 19 20:13:29 CST 2007
Just a guess if you have set a reference to word, remove it It could be confused if there are two versions of word installed or your version of word points to the wrong reference. I just noticed this happening with a new install of IE7 over IE6 and a reference set to shodvc.dll (sic) Beach Access Software wrote: >I changed Dim objWord As Word.Application to Dim objWord As Object trying >for Late Binding (like I know what I'm doing). But no soap. Same >Automation Error. > >Any ideas anybody? > >MTIAA > >Rocky Smolin >Beach Access Software >858-259-4334 >www.e-z-mrp.com > > >-----Original Message----- >From: accessd-bounces at databaseadvisors.com >[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Beach Access >Software >Sent: Friday, January 19, 2007 1:59 PM >To: 'Access Developers discussion and problem solving' >Subject: [AccessD] Automation Error > >Dear List: > > > >My client is getting an automation error in the Set ojbWord statemenet below >although the code works on my machine. I have checked to see that the Word >11.0 object library is checked in references on his machine. What else >could cause this problem? > > > >Dim objWord As Word.Application > >Dim objWordDoc As Word.Document > > > >Set objWord = CreateObject("Word.Application") > > > >With objWord > > 'Visible is set True in order to view the operation. > > .Visible = True > > .Documents.Open (Me.fldFABWorkInstructions) > >End With > > > >Set objWord = Nothing > > > >MTIA, > > > >Rocky Smolin > >Beach Access Software > >858-259-4334 > >www.e-z-mrp.com > > > > > -- Marty Connelly Victoria, B.C. Canada