Office XP error after Office 2003 update

L

leviculus

Thanks for the advice. I uninstalled MSO 2003 and repaired MSO XP
(necessary). At this point the registry values had just one string in them
and Excel 2002 VBE help worked fine. I then installed MSO 2003 in \Office03
and the original help failures returned. What problems do you avoid with the
separate folder installations?
 
L

leviculus

Thanks for the advice. I uninstalled MSO 2003 and repaired MSO XP
(necessary). At this point the registry values had just one string in them
and Excel 2002 VBE help worked fine. I then installed MSO 2003 in \Office03
and the original help failures returned. What problems do you avoid with the
separate folder installations?
 
L

leviculus

Thanks for the advice. I uninstalled MSO 2003 and repaired MSO XP
(necessary). At this point the registry values had just one string in them
and Excel 2002 VBE help worked fine. I then installed MSO 2003 in \Office03
and the original help failures returned. What problems do you avoid with the
separate folder installations?
 
L

leviculus

Thanks for the advice. I uninstalled MSO 2003 and repaired MSO XP
(necessary). At this point the registry values had just one string in them
and Excel 2002 VBE help worked fine. I then installed MSO 2003 in \Office03
and the original help failures returned. What problems do you avoid with the
separate folder installations?
 
L

leviculus

Thanks for the advice. I uninstalled MSO 2003 and repaired MSO XP
(necessary). At this point the registry values had just one string in them
and Excel 2002 VBE help worked fine. I then installed MSO 2003 in \Office03
and the original help failures returned. What problems do you avoid with the
separate folder installations?
 
L

leviculus

Thanks for the advice. I uninstalled MSO 2003 and repaired MSO XP
(necessary). At this point the registry values had just one string in them
and Excel 2002 VBE help worked fine. I then installed MSO 2003 in \Office03
and the original help failures returned. What problems do you avoid with the
separate folder installations?
 
L

leviculus

Thanks for the advice. I uninstalled MSO 2003 and repaired MSO XP
(necessary). At this point the registry values had just one string in them
and Excel 2002 VBE help worked fine. I then installed MSO 2003 in \Office03
and the original help failures returned. What problems do you avoid with the
separate folder installations?
 
L

leviculus

Thanks for the advice. I uninstalled MSO 2003 and repaired MSO XP
(necessary). At this point the registry values had just one string in them
and Excel 2002 VBE help worked fine. I then installed MSO 2003 in \Office03
and the original help failures returned. What problems do you avoid with the
separate folder installations?
 
L

leviculus

Thanks for the advice. I'd already tried this. MSO XP repair flips the
strings around and Excel 2002 help works. MSO 2003 repair flips them back so
everything fails again.

The files aren't overwritten. MSO XP files are in the office10 subfolder
and MSO 2003 files are in the office11 subfolder. My theory has Office
components identified by a component guid and a version guid. This method
isn't used with these registry values. There is just a component guid and
any version information is in each of the REG_MULTI_SZ strings and something
in MSO XP is assuming the first string is the one it wants, I think. MSO
2003 may be doing it right.
 
L

leviculus

Thanks for the advice. I'd already tried this. MSO XP repair flips the
strings around and Excel 2002 help works. MSO 2003 repair flips them back so
everything fails again.

The files aren't overwritten. MSO XP files are in the office10 subfolder
and MSO 2003 files are in the office11 subfolder. My theory has Office
components identified by a component guid and a version guid. This method
isn't used with these registry values. There is just a component guid and
any version information is in each of the REG_MULTI_SZ strings and something
in MSO XP is assuming the first string is the one it wants, I think. MSO
2003 may be doing it right.
 
L

leviculus

Thanks for the advice. I'd already tried this. MSO XP repair flips the
strings around and Excel 2002 help works. MSO 2003 repair flips them back so
everything fails again.

The files aren't overwritten. MSO XP files are in the office10 subfolder
and MSO 2003 files are in the office11 subfolder. My theory has Office
components identified by a component guid and a version guid. This method
isn't used with these registry values. There is just a component guid and
any version information is in each of the REG_MULTI_SZ strings and something
in MSO XP is assuming the first string is the one it wants, I think. MSO
2003 may be doing it right.
 
L

leviculus

Thanks for the advice. I'd already tried this. MSO XP repair flips the
strings around and Excel 2002 help works. MSO 2003 repair flips them back so
everything fails again.

The files aren't overwritten. MSO XP files are in the office10 subfolder
and MSO 2003 files are in the office11 subfolder. My theory has Office
components identified by a component guid and a version guid. This method
isn't used with these registry values. There is just a component guid and
any version information is in each of the REG_MULTI_SZ strings and something
in MSO XP is assuming the first string is the one it wants, I think. MSO
2003 may be doing it right.
 
L

leviculus

Thanks for the advice. I'd already tried this. MSO XP repair flips the
strings around and Excel 2002 help works. MSO 2003 repair flips them back so
everything fails again.

The files aren't overwritten. MSO XP files are in the office10 subfolder
and MSO 2003 files are in the office11 subfolder. My theory has Office
components identified by a component guid and a version guid. This method
isn't used with these registry values. There is just a component guid and
any version information is in each of the REG_MULTI_SZ strings and something
in MSO XP is assuming the first string is the one it wants, I think. MSO
2003 may be doing it right.
 
L

leviculus

Thanks for the advice. I'd already tried this. MSO XP repair flips the
strings around and Excel 2002 help works. MSO 2003 repair flips them back so
everything fails again.

The files aren't overwritten. MSO XP files are in the office10 subfolder
and MSO 2003 files are in the office11 subfolder. My theory has Office
components identified by a component guid and a version guid. This method
isn't used with these registry values. There is just a component guid and
any version information is in each of the REG_MULTI_SZ strings and something
in MSO XP is assuming the first string is the one it wants, I think. MSO
2003 may be doing it right.
 
L

leviculus

Thanks for the advice. I'd already tried this. MSO XP repair flips the
strings around and Excel 2002 help works. MSO 2003 repair flips them back so
everything fails again.

The files aren't overwritten. MSO XP files are in the office10 subfolder
and MSO 2003 files are in the office11 subfolder. My theory has Office
components identified by a component guid and a version guid. This method
isn't used with these registry values. There is just a component guid and
any version information is in each of the REG_MULTI_SZ strings and something
in MSO XP is assuming the first string is the one it wants, I think. MSO
2003 may be doing it right.
 
L

leviculus

Thanks for the advice. I'd already tried this. MSO XP repair flips the
strings around and Excel 2002 help works. MSO 2003 repair flips them back so
everything fails again.

The files aren't overwritten. MSO XP files are in the office10 subfolder
and MSO 2003 files are in the office11 subfolder. My theory has Office
components identified by a component guid and a version guid. This method
isn't used with these registry values. There is just a component guid and
any version information is in each of the REG_MULTI_SZ strings and something
in MSO XP is assuming the first string is the one it wants, I think. MSO
2003 may be doing it right.
 
L

leviculus

Thanks for the advice. I'd already tried this. MSO XP repair flips the
strings around and Excel 2002 help works. MSO 2003 repair flips them back so
everything fails again.

The files aren't overwritten. MSO XP files are in the office10 subfolder
and MSO 2003 files are in the office11 subfolder. My theory has Office
components identified by a component guid and a version guid. This method
isn't used with these registry values. There is just a component guid and
any version information is in each of the REG_MULTI_SZ strings and something
in MSO XP is assuming the first string is the one it wants, I think. MSO
2003 may be doing it right.
 
A

Anne Troy

I have 4 versions of Office running. They are stored in:
c:\office97
c:\office00
c:\office02
c:\office03
I have no difficulties at all.
************
Hope it helps!
Anne Troy
www.OfficeArticles.com
 
A

Anne Troy

I have 4 versions of Office running. They are stored in:
c:\office97
c:\office00
c:\office02
c:\office03
I have no difficulties at all.
************
Hope it helps!
Anne Troy
www.OfficeArticles.com
 
A

Anne Troy

I have 4 versions of Office running. They are stored in:
c:\office97
c:\office00
c:\office02
c:\office03
I have no difficulties at all.
************
Hope it helps!
Anne Troy
www.OfficeArticles.com
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Error Starting MS Help 3
Upgrading from Office XP/2002 to Office 2003 6
Can't reinstall Office Pro 2003 2
Updated from 2002 to 2003 but now I have both! 27
2003 to 2007--2003 will not uninstall, 2007 pro plus will not inst 1
MS Office 03 Update - wrong key error 6
Office 2003 / Office XP Shortcut Bar 43
Office 2003 remains after upgrade to 2007 4

Top