FIXED: [x64] - problems opening .xls, .xlsx and .docx files

[menes]

FIXED IN beta 2

I have Office 2010 64bit installed. When I double click an xlsx file I'm always getting the dialog

<FILE> is locked for editing.

If I try to open an xls file I got the error
"---------------------------
Total Commander
---------------------------
Error executing program! (31)
---------------------------
OK
---------------------------"

I got also the same error when trying to open a .doc file while the ".docx" file seem to open without problem.

Both for .doc and .docx the open command is
"C:\Program Files\Microsoft Office\Office14\WINWORD.EXE" /n "%1"

Also both for .xls and .xlsx the open command is
"C:\Program Files\Microsoft Office\Office14\EXCEL.EXE" /dde

With TC 7.56 the files open by double clicking without any of the above happening.[face=arial][/face]

[gerhard.weinberger]

I can confirm this for xlsx files.

I got the same error in Excel 2010 with TC 8.0 64. After that I was
not able to open the file with tc 7.56 anymore!

After closing tc 8.0 opening the file with tc 7.56 was possible!

[HolgerK]

Win7 Ultimate x64 / Office 2010 x86 / TC 8.0ß1 x64

Partially Confirmed.

I can open xlsx files, without an Error box, but Excel opens the file always with a warning that the file is already in use by another user.

But this happens only if i use doubleclick or contextmenu to open the xlsx file!

If i open the xlsx file only with <Enter> no problem occurred until i open a xlsx file once with doubleclick. Then the problem stays until i restart TC.

Regards
Holger

[menes]

@HolgerK, I got the error box only when I try to open by double click .xls file

For .xlsx files I got the warning that the file is used.

I try to use your suggestion (to press <ENTER> on the selected file) but I got the same behavior: .xlsx files are treated as locked and for .xls files I get ERROR (31)

[HolgerK]

I try to use your suggestion (to press <ENTER> on the selected file) but I got the same behavior: .xlsx files are treated as locked and for .xls files I get ERROR (31)

Strange. Maybe a difference between Office x86 and Office x64.

Btw. I have no problem to open xls files.
My open command is very similar to yours

Code: Select all

"C:\Program Files (x86)\Microsoft Office\Office14\EXCEL.EXE" /dde

for both exel.sheet.8 and excel.sheet.12

Regards
Holger

[ghisler(Author)]

Strange, TC uses just ShellExecuteEx function to open documents. Maybe an association error?

[menes]

Strange, TC uses just ShellExecuteEx function to open documents. Maybe an association error?

This also happens to my home computer with the difference that I can open ".xls" files without any further ado.

I don't know if it is related but when trying to view file properties from right click menu on an xlsx or a docx file Total Commander crashes (Unhandled Exception) and windows kill it.

There is definetaly something here.

Is there any chance that this has to do with the internal structure of .docx and .xlsx files? Actualy .docx or .xlsx files are not flat files but archives (zip format) by themselves. If you rename a docx or a .xlsx to .zip you can browse it.

Why this causes problems to TC64bit I have no idea, I don't know if it is even related but I think it was worth to mention it.

[ghisler(Author)]

Is there any chance that this has to do with the internal structure of .docx and .xlsx files?

No, TC handles them and their associations just like any other associations...

[morkork]

Confirmed here (Win 7 Pro x64). Opening any *.docx or *.xlsx by double click displays the "locked by another user"-dialog. Right click on *.docx or *.xlsx and then selecting "Properties" crashes TC. No problems with *.doc or *.xls.

[ghisler(Author)]

Hmm, no idea - currently I only have a .docx to .doc converter installed, and it launches just fine when I double click a .docx file.

The "locked by another user"-dialog might be caused by a virus scanner. Can you check with e.g. LockHunter what is locking the file, please?

[menes]

LockHunter is reporting that TCMD8b1 64bit is locking the file. The same thing happens with .docx files (though Word raises no warning).

When launcing programs for TC 7.56 lockhunter is reporting no lock (except from Excel or Word).

BTW, lockhunter (64 bit) does not work from right click. TCMD8b1 64bit reports the following error:


---------------------------
Total Commander
---------------------------
OLE2 Command failed! Either your OLE2 subsystem is damaged, or you have installed a shell extension which is incompatible with Total Commander!
---------------------------
OK
---------------------------

However Running TC 7.56a, by selectind right click/X64 works like a charm.

And remains the mystery of TCMD8b1 64bit crashing when trying to display properties of any *.docx or *.xlsx file

[menes]

All things mentioned above are fixed in TC8b2 64bit!!!

Thanks mr Ghisler

[HolgerK]

Yes, seems to be fixed in TC8.0ß2 x64

Thanks
Holger

[ghisler(Author)]

Nice to hear that! It was probably caused by the faulty exception handling in Lazarus 64-bit.

[zlatan24]

FIXED IN beta 2

I have Office 2010 64bit installed. When I double click an xlsx file I'm always getting the dialog

<FILE> is locked for editing.

If I try to open an xls file I got the error
"---------------------------
Total Commander
---------------------------
Error executing program! (31)
---------------------------
OK
---------------------------"

I got also the same error when trying to open a .doc file while the ".docx" file seem to open without problem.

Both for .doc and .docx the open command is
"C:\Program Files\Microsoft Office\Office14\WINWORD.EXE" /n "%1"

Also both for .xls and .xlsx the open command is
"C:\Program Files\Microsoft Office\Office14\EXCEL.EXE" /dde

With TC 7.56 the files open by double clicking without any of the above happening.[face=arial][/face]

For settling out given complicity you may use how to repair Excel file. It owns all necessary facilities such as scans and analyses damaged excel data. It can recover excel files after some troubles: power failures, viruses and unexpected errors.