Link to home
Start Free TrialLog in
Avatar of cornholme
cornholme

asked on

Referencing Word Object library from Access

Hi All
I have an Access 2007 frontend running under Access 2016 runtime and it works just fine. Recently the backend was move to a google drive without any problems. Then the IT guy looking after the network decides to move Office Std 2007 to the google drive, I now have problems. The Word Object library is no longer available so the access mail merge routine within Access FE fails. The question is this how do I within vba Tools References point to the Word Object Library?

Or is there another way of referencing the above Word Object Library?

Regards
cornholme
SOLUTION
Avatar of Daniel Pineault
Daniel Pineault

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of cornholme
cornholme

ASKER

Thank you  Daniel, I'll follow up on Late Binding idea.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Hi Scott,
Thanks for the comments. A bit of background maybe.  I'm the tail trying to wag the dog here, and failed dismally. I wrote a multi-user(6) Access database with local FE's and server based BE about 10 years ago and its worked fine until 3 weeks ago when the client moved their office. Scrapped their server and move data storage to google drive. I played no part in this move. I became focus of attention last Monday with a call that "your database has failed". The IT guys had done real good job trashing the db during the migration to the new kit.  So one the jobs to do find how to refer to Word Object Library so the mail merge can be run. It appears that the simple solution is to reinstall Word on the local machines rather than refer to the google drive, which I've no knowledge of, and late binding I don't think will solve the issue. A Word Object Library reference is needed, which is presently absent

 You mentioned data corruption that little rascal has already paid a visit. That is another job!

So Daniel and Scott thank you for your help. Your comments have been very useful.

regards
cornholme
Your primary concern should be moving the database back locally (within a wired LAN for standard setups).  Their IT guy obviously knows nothing of Access and this should be highlighted quite rapidly as this is jeopardizing their data!  This should be obvious by the simple fact the db worked for 10 years, up until the time it was migrated.  Then add to that the fact that automation is no longer functional... doesn't take a rocket scientist to figure out things need to be put back the way they are, or speak to someone (ie you) who know what setups can work with Access.

I hope you're charging by the hour on this one.
I'd approach the client with Daniel's suggestion - or perhaps suggest a rewrite to a web-based product at about 30X the cost of the Access system. That generally gets them to light up the IT guy pretty quick :)
Cheers guys for the Support! The idea of lighting up the IT guy is a really good suggestion.  I am charging by the hour and as its Xmas its time for a pay rise.  

The job is stopped presently waiting for the internal IT Guy.

Kind regards

cornholme