Problems with Access 2007 & 2010 Runtime

Topic

New Reply

I’ve had clients use the runtime before, but I have 1 client where I’m having continuing problems. Here is the code I’m using for opening a Mail Merge document:

dim oApp as object

Set oApp = CreateObject(“Word.Application”)
oApp.Visible = True
oApp.Documents.Open QU() & strDoc & QU()
oApp.ActiveDocument.MailMerge.OpenDataSource Name:=”c:contactNamesForPostcards.txt”
oApp.ActiveDocument.MailMerge.Destination = 1

QU() is just a function that returns a double-quote, and strDoc contains the document name (including path).

They had various full versions of Access (from 2000 to 2007), and it worked. Then some workststions were updated first to Access 2007 runtime (and later 2007 runtime) so we could upgrade the db to a .accdb database.

Now, when any of the runtime versions try this they get an “ActiveX component can’t create object” error (#429). They do have Word.

Is this just a deficiency in the runtime that won’t let use this? I haven’t tried it yet, but I also use a similar method to open and control an Excel spreadsheet, and I have a hunch that won’t work either.

Reply | Quote

Replies

I must say I don’t have much experience with automation with Word (usually do it with Outlook or Excel), so I am not sure which library you need to reference to be able to create a word app. Do you have that reference, for the Word version they have installed?

Reply | Quote

I must say I don’t have much experience with automation with Word (usually do it with Outlook or Excel), so I am not sure which library you need to reference to be able to create a word app. Do you have that reference, for the Word version they have installed?

No, I’m using late binding, which eliminates the need for a reference.

I think my problem may not be with Access, but with Word; I’m not sure it is properly registered as an automation server. The client is using Windows 7 and office2010, and you can’t even find a WinWord.exe anywhere! The shortcut to execute Word has this:

“C:Program Files (x86)Common Filesmicrosoft sharedVirtualization HandlerCVH.EXE” “Microsoft Word 2010 9014006104090000”

Reply | Quote

Yeah, it looks like the issue is with Word. Seems Office was installed with Click to Run technology, which would explain the fact that you have Office Virtualization Handler handling the calls to word.
Seems automation issues when using it are not new: http://social.msdn.microsoft.com/Forums/is/visualfoxprogeneral/thread/c720813f-cf15-4e26-b205-e1d2530d0faf

See if the advice in that thread is of any help.

Reply | Quote

Yeah, it looks like the issue is with Word. Seems Office was installed with Click to Run technology, which would explain the fact that you have Office Virtualization Handler handling the calls to word.
Seems automation issues when using it are not new: http://social.msdn.microsoft.com/Forums/is/visualfoxprogeneral/thread/c720813f-cf15-4e26-b205-e1d2530d0faf

See if the advice in that thread is of any help.

Thanks for the link. That seems to exactly address the problem. Now I’ve just got to see if I can make it work!

Reply | Quote

No problem, hope it works :).

Reply | Quote