-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
zip path is too long #719
Comments
readxl only uses base R facilities in the internal helper where this is coming from: https://github.com/tidyverse/readxl/blob/main/R/xlsx-zip.R So the answer for now is that this path truly is problematic for readxl, because there's not some quick fix we can make in our code. I know you say have activated long paths, but here's someone reporting success with that method, pointing to exactly the same article: It looks like openxlsx uses a 3rd party library to access the files inside the |
And another lead re: something to check on your system: |
I have by no means digested all of the content in this post, but it gives me hope that perhaps the problem is going to be fixed at the source, i.e. in R itself, in the not-too-distant future: https://blog.r-project.org/2023/03/07/path-length-limit-on-windows/ |
I'm sorry, I had not seen the responses in this thread. I made the change in gpedit.msc and restarted also but the problem persists. |
It is possible that the next version of R will handle long paths better and solve this for us. |
Hello! This is now working without problems! |
I am in windows and I have a certain folder structure. I have a database that I try to import with
readxl::read_excel(
), however I get the following error:I have copied the same file to the same location in .sav and .dta format with the haven package and it reads normally. I have also activated long paths as suggested here (https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=powershell), but it still does not work.
Created on 2023-02-05 with reprex v2.0.2
Session info
The text was updated successfully, but these errors were encountered: