Unable to Open Macro Storage on Export from Access to Word


Before you say anything, I did see "that MS KB article" that everyone talks about when this question is posted, but it didn't help. I am running on Windows XP, with local admin rights, and the code works fine. A user then comes and log into my machine (losing local admin) and they get the Unable to open macro storage error, failing on:

Set WordDoc = WordApp.Documents.Open(FileName:="C:\FSBDB\q3-blank.doc")

Is there any way around this? The document is a word form (form fields) that I am dumping data into from the database table.. It works SO beautifully when I do it and it'd just kill me if I couldn't use it because of permissions.

Here's the complete code:
If WordApp Is Nothing Then
    Set WordApp = New Word.Application
    Set WordApp = GetObject(, "Word.Application")
End If

If err.Number <> 0 Then
End If

On Error GoTo 0

WordApp.Visible = False

Do While Not rs.EOF

Set WordDoc = WordApp.Documents.Open(FileName:="C:\FSBDB\q3-blank.doc")

    Bookmarks("txtTitle").Range.Fields(1).Result.Text = rs!Title
    .FormFields("lstDivision").Result = rs!Division
    .FormFields("lstCoreBusiness").Result = rs!CoreBusines
    .FormFields("lstProgram").Result = rs!SubItem
    .FormFields("lstThroneSpeech").Result = rs!ThroneSpeech
    .FormFields("lstBudget").Result = rs!Budget
    .FormFields("lstKeyStrategies").Result = rs!KeyStrategy

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

jadedataMS Access Systems CreatorCommented:
Hey Mitchell_!

  This sounds more like a Word error being passed thru to Access.

  See this link:  http://www.support.softwaretechnology.biz/main/R10650.htm about mid page regarding your dilemma.
  See also: http://dbforums.com/arch/219/2003/1/666622  this refers to the MSKB thing but there's more.

Mitchell_Author Commented:
Thanks but..

I don't see how it could be a word error when the export works fine under my administrative account.. It's just when a 'regular user' tries it that it fails.. wouldn't that mean permissions?

any other thoughts?
jadedataMS Access Systems CreatorCommented:
Access permissions don't mean anything to a Word Document.

There is some |other| difference in operations when your other user is logging on.
If you want to completely rule out a permissions issue, put that user in the Admins group (or your SuperGroup) and try the op again.
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

I woud say that it could be a rights issue. Check where the temp directory points to when the user logs in and make sure the user can create files in this directory.
Jack Mitchell means Operatings System permissions, not access permissions.
jadedataMS Access Systems CreatorCommented:
Which version of MS-Office.
(Office97 has specific permissions issueswhen run on Win2000 or later).

Mitchell_Author Commented:
it's office 97 - you know of something offhand with O97 and macros?
Office 97 macros do not run on Win2000 and later for non-privileged users without registry changes.
I'll try to find the KB article.

Mitchell_Author Commented:

Thank you for the article. That's definetly been confirmed as the problem.

Now, My problem is that I do not have admin access on any machine other than my own to apply this fix, and the IT folks definetly won't want to update 100+ machines to accomdate my little application.

Is there another way to get this data out to word via access into these form fields?

I can't say whether there is any other solution.  In a way you have to hope there isn't, because it is a security issue at heart.
I have come across this issue in several customer sites.  In every case it has been resolved through the recommended registry changes.  It is a pretty fundamental issue for Office 97 users and I can't see how any site can run Office97 with the constraints the problem imposes.

I know very little about Windows admin, but if you have that many users there must a good chance that the required changes can all be done from a central point.  Show someone the KB article.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Mitchell_Author Commented:

Thank you. I'll do that.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.