A family of Microsoft word processing software products for creating web, email, and print documents.
Over here (Snow Leopard) the Finder enforces a 255 max length in folder and file names. However, Word seems to stop at 246 characters for file names (but not for folders). Even if I nest five or six 255-character folder names, Word does open the file as long as the name has 246 characters or less. Attempting to open a file with longer names produces a "File not found" error.
On my iMac, the file name you provided (109 charactrers) did not cause any problem.
I have been tracking several "Word 2011 Cannot Open File" threads on various systems. There seem to be several manifestations:
1) Supposedly invalid character in filename.
2) Supposedly invalid character somewhere in the pathname (including name of hard drive).
3) Filename itself too long.
4) File existing on a server somewhere (problem possibly stemming from 1-3 above).
For me (on OS X 10.7.5; I don't remember which cat this is), I have the issue baked down to a single problem (local hard drive only):
Word 2011 (purchased via Office 365 product) WILL NOT OPEN a file, either by double-click or from Open Dialog, if the PATHNAME has a SEMICOLON in it. If the filename itself has a semicolon, it opens no problem. But if a semicolon is in ANY folder name in the path, no can do. This is totally reproducible. Remove semicolons from folder names, file will open. Put semicolon back in, no can do.
Guess what: I use tons of semicolons in folder names. So, Word 2011 is basically unusable for me. I refuse to rename folders to use the product; I refuse to pull every document I want to use to the desktop and then return it to the offending semicolon-burdened folder after I'm done.
As others have noted, Excel 2011 and PowerPoint 2011 do NOT seem to have this problem.
Other testing: for me, other supposedly invalid characters (including slash, backslash, bullet, and others) in the path do not cause a problem. Oddly, a slash in the filename itself DOES make the file "no open." Go figure.
HERE'S THE BIG QUESTION: After 4 years and these postings all over the universe, Microsoft is definitely aware of this ridiculous bug in JUST ONE of their flagship modules of Office. Why no fix?! When will it get fixed?! I mean, come on guys! Ask the Excel 2011 team, or even the Word 2008 team, how they pulled off the amazing feat of opening a file with a ";" in the pathname. Make us proud!