Increase the 218 character filename length limit to open files in excel
Excel can't open files with full path lengths greater than 218 characters as documented in https://support.microsoft.com/en-us/kb/213983. This is still a problem in Office 2016. It seems crazy that Excel can't open a valid file that the filesystem allows. People have been complaining about this since Office 2000. The thread below has over 11 thousand views and there are plenty others. Please fix this. http://answers.microsoft.com/en-us/office/forum/office2013release-excel/sorry-unable-to-find/595333d0-1463-499f-967e-4da8ac2e2047
I am excited to announce that we have completed the work to enable longer file name and paths in Excel for desktop. This was a significant change that required work on multiple parts of the product beyond open and save, since the file path is used in other features like external links.
Before this change, Excel for desktop could open and save files with a full path length of up to 218 characters.
Starting a few weeks ago, all Office 365 users in the monthly channel (CC – current channel, build 12624.20466 or above) are able to open and save files up to 2034 characters. However, in practice there are lower limits imposed by the file system:
- Windows local and UNC files: 260 characters
- OneDrive/SharePoint files synced to the local drive: 260 characters
- OneDrive/SharePoint files opened directly from the cloud: 400 characters
Thanks again for your continued feedback.
David [Microsoft Excel Team]
cannot believe.. In 2019 this is still an issue. With NTFS filesystem and computers with 8-16-32..etc Gb memory. They focusing on annoying useless features like "Ideas" in Excel..etc. But really important problems are not fixed.
Only excel have been limited to 218 characters, other files are 260 character limit i believe hence why the pdf files work fine for you. Glad to see they have finally started working on it. We hope we don't wait another year or 2 before rolled out.
To add to this; I have found that I can save pdf files which go beyond the 218 limit but not the exact same excel file name! As an example: I receive pdf files which I save to a certain folder, and I create an excel file to instruct our Accounts Payable team to pay the invoice on the received PDF. So that I can match the invoice to the payment instruction I save them with the exact same name but the corresponding extension, but the Excel file won't save because it is 10 characters over the limit and I have to truncate it!
Very frustrating and surely there's no good reason for it in this day and age.
Please for the love of god fix this!
It would also be helpful to release a work around ?🙏
Stuart Bailie commented
David thanks for the update. Is there a loose guess to a time line? Can we see the feature in O365 Office next quarter? Next year?
Gerald Platzer commented
Still a big issue for our user community. This has to be resolved ASAP.
Gerald Platzer commented
Still a big users for my user community. This has to be resolved ASAP.
Still not listed in the 365 Roadmap - could this please be added so it can be acknowledged formally?
This is really an annoying issue - to open files with long paths I have to move them to my workspace, and then when I am done I have to move them back again. Is is incredible that this issue is still not solved.
Justin Mosebach commented
Seriously, what is this... 1993?
I need to keep my files in folders order arranged as I am working in a project with multiple countries.
This is not agreeable that only 218 characters is agreed in such situation.
Afruja Aktar Mili commented
Please help to increase characters from 218 characters of Office 2016. It's crazy! If you already worked on it, please suggest the possible way. Thanks
Gary Wernick commented
Please fix this - you have four years to have resolved this now.
a Rough ETA would be great rather than another 8 month wait for another update - 2019/ early 2020/late 2020?
It is not in the roadmap that I can see. Pretty disappointing that this is still an issue.
Chris Paesano commented
Is this listed in a Roadmap somewhere?
Victor Fernandez commented
@David, can you tell us what is a ballpark ETA for this solution?