[ms office - xp] Compatibility Pack opens files read-only

[enjay]

We have the Office 2007/2010 compatibility update installed site-wide, and this works fine on all except one computer. Generally, when you open a xlsx file, Excel launches and then says it is converting the file, which then opens; on this one computer, however, a dialog box appears before Excel opens saying it is converting, and Excel then launches with the spreadsheet open but called X000001.xls [Read-Only], which is saved in a local temp file somewhere.

 

Any ideas? I've tried re-installing the compatibility update, and even re-installed Office, but without success.

[GREED]

Are there any other MS updates to apply on this PC?

[enjay]

Just the usual monthly updates, all of which should be on.

[GREED]

It could be a legacy issue stored in the profile. Try deleting that profile (or a test one)? Or even simpler, use a new/different account and see if the same issue?

[enjay]

Don't think so - all users (including my administrative one) are affected. Also, the same users are unaffected on other computers.

[GREED]

Unknown then, but I wouldn't spend too much extra time on it if you could rebuild the PC just as quickly? Unless of course someone has a bright idea soonish?

[sparkeh]

Compare the file associations on the effected machines and the working machines.

This can happen if the 2007 file formats are passed to something like.. can't rememeber the exact program but something like 'MS XML processor' before going to excel.

[BatchFile]

I've got this as well on a teacher laptop - current workaround is to open Excel first then use file-open, which works fine:confused:

[sparkeh]

Compare the file associations on the effected machines and the working machines.

This can happen if the 2007 file formats are passed to something like.. can't rememeber the exact program but something like 'MS XML processor' before going to excel.

 

Just checked, make sure .xlsx files are associated with Excel and not with Microsoft Open XML Converter

[enjay]

Rebuild isn't ideal given the location of the computer (it could wait until Christmas hols, though); File>Open would work, but isn't generally the way people access their files.

 

I'll check sparkeh's suggestion for file associations...

[GREED]

Rebuild isn't ideal given the location of the computer (it could wait until Christmas hols, though); File>Open would work, but isn't generally the way people access their files.

 

I'll check sparkeh's suggestion for file associations...

 

Of course it isn't ideal, and is a lame suggestion (to most things!) but is worth a consideration only against how long you might spend on solving the problem. solve in a day? cool. Solve in a week? not so cool

[enjay]

Of course it isn't ideal, and is a lame suggestion (to most things!) but is worth a consideration only against how long you might spend on solving the problem. solve in a day? cool. Solve in a week? not so cool

 

There is also the impact on the user to consider, though. I could rebuild the PC which would get the problem off my desk in 5 minutes but mean they can't use their computer for 4 hours, or I could spend 30 minutes spread across a few days finding a solution which can then be applied in 5 minutes.

[GREED]

There is also the impact on the user to consider, though. I could rebuild the PC which would get the problem off my desk in 5 minutes but mean they can't use their computer for 4 hours, or I could spend 30 minutes spread across a few days finding a solution which can then be applied in 5 minutes.

 

Of course, and that 30 minutes is nothing, so you have the right plan. I am a Trainer and work with IT apprentices, and one thing these very technical guys don't do is if they have an issue, look at the quickest, most suitable and most permenant solution, as opposed to scouring the internet forums for a hack or fix or flash that takes days and days. One chap spent 3 weeks trying to fix a switch issue with flashes and hacks, and a quick call the manufacturer would have found it was a fault with the model. Boss was not pleased!

[enjay]

Just checked, make sure .xlsx files are associated with Excel and not with Microsoft Open XML Converter

 

Yeah, spot on sparkeh, that's the problem.

 

The thing is, I can't enter the correct information in there. Checking a working PC, the files should be set to open with Excel, and under the Advanced section, the &open command should run "C:\Program Files\Microsoft Office\OFFICE11\EXCEL.EXE" /e, but whenever I enter that manually, it decides to add a %1 at the end, and then doesn't work.