Excel 2003 File Type issues when Compatibility Pack installed

Our company uses Excel 2003 with the compatibility pack since it came out.  In the last year or so, we seem to be fighting an issue on certain computers opening .xlsx files from Outlook attachments or Windows Explorer.  When looking at the xlsx file type 'Open' properties, the filepath reads
"C:\PROGRA~1\MICROS~2\Office11\EXCEL.EXE" /e
instead of
"C:\Program Files\Microsoft Office\Office12\EXCEL.EXE" /e
What is up with the DOS filepath syntax?
This DOS filepath syntax causes problems with MacroButtons within Excel.  We use a macro file with a custom toolbar loading from the 'XLSTART'.  When is Excel is started up by itself, the macro file references it's normal Windows Filepath, but when Excel is started by opening a XLSX attachment the macro file opens referencing the DOS filepath sytax, which causes the MacroButtons to have bad filepath (the toolbar is remains active from the previous session).  

We have tried manually changing the xlsx File Type Open properties back to '"C:\Program Files\Microsoft Office\Office11\EXCEL.EXE" /e', but this change will not stick (property still displays the DOS filepath the next time the Open property is edited the next time.   We unsuccessfully have tried  Start-Run:  Excel /unregserver & then Start-Run:  Excel /regserver;  reinstalling the Compatibility Pack.

Is there a way to force the File Type filepaths to use the Windows filepath syntax instead of the DOS filepath syntax that the Office Compatibility Pack seems to force them to?
This is somewhat related to Q_26755895.  
LVL 1
Jeff GeiselmanAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
TommySzalapskiConnect With a Mentor Commented:
Look here
\HKEY_CLASSES_ROOT\Excel.Sheet.12\shell\Open\command
0
 
TommySzalapskiCommented:
Have you tried changing the path in the registry instead of from Control Panel?
0
 
TommySzalapskiCommented:
If you don't see Excel.Sheet.12 then check the default value in HKEY_CLASSES_ROOT\.xlsx to see what your computer is calling it.
0
 
Jeff GeiselmanAuthor Commented:
Thanks for the Registry suggestion and registry location.  I will try that on a few of the computers that are exhibit the problem and let you know how it works.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.