Document execution problems

[ibonny]

Good morning,

I've attempted to fix this problem by scanning the boards for related issues, and I found two... the "space issue", and the "execution style issue". Neither fix appears to work. The problem is the following: I have a spreadsheet file (.xls) that I can double-click in explorer and launch successfully. If I search for it in FARR and hit enter, since its the first match, FARR closes, and does nothing. I've attempted to change the execution method (through preferences->general->use document launcher help utility and its options) and neither work. I've also checked for spaces before and after the filename, and it doesn't have any. Also, if I right-click the file and try properties or "shell context menu", I can't get either to pop up. Is there a directory size limit to the match? I'm using a document under the start menu in Windows 7, which is buried quite deep directory-structure wise.

Thanks,

Ian

[ibonny]

Hmm.. it appears to be only that one particular XLS spreadsheet. I tried a few others, and they launch perfectly. (Also, .xlsx files as well.) I'm still attempting to discover what makes it unique. I'm launching other XLS and XLSX files from the same directory, so its not the directory length limit I was talking about earlier.

[mouser]

i think you were on the right track regarding the possibility of spaces in the file names -- or perhaps other unusual characters -- maybe try making a copy of the file in the same directory, and renaming the file?

[ibonny]

Ok, I'll give that a try.. but there are no spaces at the beginning or end... and it has internal spaces, but so do other files I have that I open on a regular basis.

[ibonny]

ARGH! That's what it was... there was a space AFTER the filename, but BEFORE the extension. I was looking for spaces AFTER the extension. Sorry about that.

[skajfes]

I was just typing up an elaborate answer, but the issue got solved in the meantime

@mouser: I think this really is a bug of sorts, can you do something about it?
From what I can tell, FARR finds the file and then trims the filename prior to execution. Note that the filepath at the bottom is correct, as is when you copy the filename using ctrl+c.

[mouser]

yes i shall fix.