Our organization is partway through an upgrade from Office97 to OfficeXP. We
have a lot of Excel files with macros, and on some PCs, there is an issue
with it "failing to compile" and having errors (hard for me to test, because
I'm in a different location and I'm one of the lucky ones with a PC that
works).

Troubleshooting over the phone, it appears the issue is under (VBA)
tools/references had Microsoft Office 8.0 checked, and it is now missing. I
had a user uncheck that, and instead check the Microsoft Office 9.0 (I'm not
sure why, mine says 10.0 but hers says 9.0). The file ran (woot!) but she
then called back and said that it "didnt save the setting" when she went to
run it again.

I don't know enough to know what is going on- is this setting in the file
itself, in which case we have hundreds (literally) of files that need to be
changed, or is it something that should only have to be changed once, but
maybe our "locked down" applications aren't allowing the setting to take on
her computer? If anyone can give any insight as to whether those reference
settings are file-specific vs global to excel, would be greatly appreciated!

Thanks,
Keith

The 9.0 reference is for Office 2000. I suspect the user has office 2000.
Further, a worksheet being brought up from xl97 should automatically work
(as in your case). It sounds like a mixed bag here. I suspect someone
subsequently opened it in xl 2002, where the reference was set to 10.0, then
when opened in 2000, it became confused because it has never heard of
xl2002.

That said, I haven't seen many reported problems of this nature between xl97
through and including xl2003. So I don't think it is inherent. My only
guess would be that some users have a standard location where office is
installed and some have a non-standard installation or have shared files on
the network or something that is causing/contributing to the problem. So I
could be wrong on the multiple versions, but 9.0 is xl2000. In any event,
once the reference is made, it should not revert back if it is only used on
the same machine or identical machines.

sorry I can't be more definitive on this - but I haven't had to deal with
such a situation - perhaps another contributor has more first hand
experience.

--
Regards,
Tom Ogilvy


"Keith R" wrote in message
...
Our organization is partway through an upgrade from Office97 to OfficeXP.
We
have a lot of Excel files with macros, and on some PCs, there is an issue
with it "failing to compile" and having errors (hard for me to test,
because
I'm in a different location and I'm one of the lucky ones with a PC that
works).

Troubleshooting over the phone, it appears the issue is under (VBA)
tools/references had Microsoft Office 8.0 checked, and it is now missing.
I
had a user uncheck that, and instead check the Microsoft Office 9.0 (I'm
not
sure why, mine says 10.0 but hers says 9.0). The file ran (woot!) but she
then called back and said that it "didnt save the setting" when she went
to
run it again.

I don't know enough to know what is going on- is this setting in the file
itself, in which case we have hundreds (literally) of files that need to
be
changed, or is it something that should only have to be changed once, but
maybe our "locked down" applications aren't allowing the setting to take
on
her computer? If anyone can give any insight as to whether those reference
settings are file-specific vs global to excel, would be greatly
appreciated!

Thanks,
Keith