Excel embedded in Word doc causing problems with Access Runtime

[Joel Moore]

I have Office XP Standard (or Small Business--I forget which) installed on
a couple of machines here. We run an application that requires Access and
comes with Access 2000 runtime. After installing the runtime we have the
following problem:

If we open a Word document that has an embedded Excel spreadsheet and
double-click on the spreadsheet to open it, or if we try to embed a
spreadsheet into a new Word document, a dialog pops up saying something
about configuring Access 2000 runtime (what you normally see when using
Office features that were configured to be "Install when needed"). We then
get an error message:

"Error 1706: No valid source could be found for product Microsoft Access
2000 Runtime. The Windows installer cannot continue."

I click "OK" and the process starts up again. It'll repeat continuously
until you manage to click "Cancel" in the first dialog.

So WTF? Why is the Windows installer trying to install something? How can
I prevent this?

Also, it only happens with the user accounts on the machine which are all
configured as Power Users (since Limited accounts are so absolutely &$@#!
useless). The administrator account does not have this problem.

Thanks,

Joel Moore

 

[Bob Buckland ?:-\)]

Hi Joel,

Error 1706 is not being able to access the original
installation media/location for Office. The installer
can be adding or repairing a file.

If MS Access is installed on the machine then the
Runtime package may not install (same name as the app for the .exe)

=========
I have Office XP Standard (or Small Business--I forget which) installed on
a couple of machines here. We run an application that requires Access and
comes with Access 2000 runtime. After installing the runtime we have the
following problem:

If we open a Word document that has an embedded Excel spreadsheet and
double-click on the spreadsheet to open it, or if we try to embed a
spreadsheet into a new Word document, a dialog pops up saying something
about configuring Access 2000 runtime (what you normally see when using
Office features that were configured to be "Install when needed"). We then
get an error message:

"Error 1706: No valid source could be found for product Microsoft Access
2000 Runtime. The Windows installer cannot continue."

I click "OK" and the process starts up again. It'll repeat continuously
until you manage to click "Cancel" in the first dialog.

So WTF? Why is the Windows installer trying to install something? How can
I prevent this?

Also, it only happens with the user accounts on the machine which are all
configured as Power Users (since Limited accounts are so absolutely &$@#!
useless). The administrator account does not have this problem.

Thanks,

Joel Moore>>
--
Hope that helps,

Bob Buckland ? MS Office Products family MVP
*Courtesy is not expensive and can pay big dividends*

http://go.CompuServe.com/MSOfficeForum?loc=us


Have a little fun with Office
http://microsoft.com/uk/office/xtra/

Get a Microsoft Certification of your Office App Skills:
http://microsoft.com/traincert/mcp/mous/requirements.asp

Try the new MS Knowledge Base Help and Support Search Tools & FAQ:
http://support.microsoft.com

Choose the newsgroups focused on your MS Office applications:
via Browser:
http://communities.microsoft.com/newsgroups/default.asp?icp=prod_office
by Newsreader: (Outlook Express)
news://msnews.microsoft.com

 

[Joel Moore]

Hi Joel,

Error 1706 is not being able to access the original
installation media/location for Office. The installer
can be adding or repairing a file.

If MS Access is installed on the machine then the
Runtime package may not install (same name as the app for the .exe)

I meant to point out that Access isn't installed (Office Standard and Small
Business versions don't come with Access).

I investigated a little more and discovered that this issue stems from a
couple of missing keys in the user's registry ("HKCU\Software\Microsoft
\Office\9.0\Access\UserData" and "HKCU\Software\Microsoft\Office\9.0\Common
\UserData" -- both need to be set to "1"). The Administrator account has
these key I suppose because the runtime was installed from that account.

Now, 2 questions:

1) I know I can simply add these keys to each user account (either manually
or using a .reg file) and hope there aren't additional missing keys but is
there a simpler way without giving all the user accounts administrative
rights?

2) Is it too much to expect Microsoft applications to install properly in a
multi-user Microsoft OS?

Joel Moore