As noted above, I no longer think the error is linked to the Excel file inside the folder. They were created by the same user and have the same read/write permissions. If the folder name is Tracking_Spreadsheet and the zipped folder is Tracking_Spreadsheet.zip it *will* unzip. If the folder name is trackingspreadsheet and the zipped folder is trackingspreadsheet.zip it *will* unzip. If the folder name is Tracking Spreadsheet and the zipped folder is Tracking Spreadsheet.zip it *will* unzip. If the folder name is Trackingspreadsheet and the zipped folder is Trackingspreadsheet.zip it *will* unzip. If the folder name is trackingSpreadsheet and the zipped folder is trackingSpreadsheet.zip it won't unzip. If the folder name is TrackingSpreadsheet and the zipped folder is TrackingSpreadsheet.zip it won't unzip. xltx file in the folder, the only thing that makes a difference is whether the name of the folder contains an upper case character part way through, when there are no gaps or underscores between the first word in the folder name and the second. So far as I can establish after multiple iterations and variations, it doesn't matter whether it is an. Mac users with multiple zip files to open can use this method. As noted above, I no longer think the error is linked to the Excel file inside the folder. Archive Utility is a built-in Mac application that can open and extract files from zip archives. Thanks.Ĭlick to expand.They were created by the same user and have the same read/write permissions. Looking forward to the helpful advice I've received here in the past. rtf Read Me file created using TextEdit, and a MS Excel 2021. In case it is relevant, the folder I'm compressing contains a. What I want is to created a zipped folder that people can unzip using the built in Archive Utility, or to find out whether this is a bug that is occurring to others. I know how to use those, and the zipped folders do open when I use Unarchiver. I'm *not* interested in suggestions to install Unarchiver or some other utility, or to use Terminal. I've also tried compressing the folder using YemuZip, which enables creation of zipped folders that don't contain the hidden resource fork files that display for, but are useless to, Windows users. At first I thought this was a problem created by the online platforms I was trying to store the file on (Google Drive, Dropbox, Wordpress, GitHub), but now that I can't even open them on my Mac immediately after creating them, it makes me think something else is going on.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |