Office 2007 Access and GetWordNT.dll problem

[michael.tredway]

Hi Marcus. Sorry, I committed the hyneus crime of contacting you direct earlier, and then read your comment on a Posting asking someone not to do that, but to post any queries here so all can benefit.

So, duly wearing sackcloth and ashes, here's the problem. I am running 10.1.02 (I know, but I can't justify an upgrade sufficiantly to persuade the wife) and have recently upgraded MS Office 2007(I don't have to pay for that, my employer does)

However, when exiting Access I keep getting a Microsoft Error Message (no change there then), and when I look a "What data does this error report contain?" the Mod Name is getwordnt.dll.

As the only copy of that .dll file resides in the Macro Scheduler folder, and that I don't get the problem if I turn Macro Scheduler off, I can only assume that Microsoft Office 2007 has a problem this aspect of Macro Scheduler.

We all know what line Microsoft will take if I ask them about it, so I resort to you. Is there a solution? How essential is this .dll file? I have renamed it, but Macro Scheduler notes that it is missing when started, although it still seems to work OK after.

Have I finally got a good reason to give the wife for me to upgrade?

[Marcus Tettmar]

Hi,

Odd, because we run Office 2007 and I have never seen this problem with any version of Macro Scheduler, from 10 onwards.

However, since v10 I think we have provided newer versions of the getword dlls. So I suppose it is possible your problem won't exist with the newer versions.

This zip file contains the versions shipped with v12:
http://www.mjtnet.com/software/getwordDLLs.zip

Unzip the two DLLs into your Macro Scheduler program folder, replacing the existing copies.

I don't know if it will make any difference but give it a try.

[michael.tredway]

Hi Marcus, those files did cure the problem, thanks.

As to why I had the problem in the first place, who's to know.

The file was dated 07/04/2008 (dd/mm/yyyy), would that be correct for the version I am using?

Anyway, if it works don't fix it, that's what I say.

Thanks again,

Mike