Copy to Excel / Office 365 - Autosave turned off message

[Jason McCleskey]

Minor nuisance but any time we export to Excel via the "Copy To Excel" or "Export Results->Excel File" option we get banner stating "AUTOSAVE TURNED OFF This workbook contains features that prevent it from using AutoSave. Please save your workbook manually". If attempt to turn on AutoSave we see message stating "Before AutoSave can save your file, you need to fix the following: The file was created in an older format. Please select File > Save As to update the file format". If we save manually and/or Save As... a new Excel workbook it still won't allow AutoSave.

Not a big deal at all because we can just use the "Copy" or "Copy with Header" functionality and paste to Excel and it's fine. We are on the below version of Pl/Sql Dev and using Microsoft Office 365 and OneDrive. I'm sure this is just a versioning issue between Pl/Sql Dev export and Office 365. Just curious if anyone else using Office 365 knows a way to avoid this?

PL/SQL Developer
Version 14.0.6.1988 (32 bit)
Windows 10 (64-bit) Build 18362

Microsoft Office 365 apps for enterprise
Excel version 2008 (Build 13127.21348)

Thanks,
Jason

 

[jhughes]

Your listed version at first confused me, given you list Office 365, until I dug into MS (https://docs.microsoft.com/en-us/officeupdates/update-history-microsoft365-apps-by-date) and saw you are on the semi-annual enterprise channel.

Are you exporting as .xls format still? I long ago switched to .xlsx. I export as .xlsx all the time via the "Copy to Excel..." right click option and I've never had any such warning from Excel. I'm using PSD v14 (and used many prior versions with no difference).

To check this, go to Preferences -> Files -> Format and for the Excel export format, set it to "XLSX format (Excel 2007 and higher)"

 

[Jason McCleskey]

Correct on the semi-annual release channel. The 2008 date surprised me too but as you note in the MS note that's the way they version it.

As for the PSD setting - yes - I have it set to Export XLSX format (Excel 2007 and higher). Screenshot attached for reference. Just for fun I toggled all the different settings off and on and tried with each way and still get the MS message every time I go to XLSX.

Only thing I haven't tried is the 64-bit PSD but I don't want to go to that because of dependency on a plug-in that is only 32-bit.

Since it's working for you it must be something else about our O365 or PSD version.

Thanks,
Jason

 

[Nicolas D.]

I have Excel version 2102 and I state the same for me (Version number format now being YYMM - your version being From August 2020 - but I agree it was looking confusing for your case. Confusion will go away at your next update).
But it also state that Autosave cannot be enabled because the file is located on your local machine.

That said, PL/SQL Developer will not be able to overcome that part, as program work locally and file are generated under the %TEMP% folder.
I am not sure Marco have plan for support of uploading the file into OneDrive directly yet.
So you are force anyway to first save to OneDrive, which will upgrade the format, and the problem will be solved automatically.

I think you get that message because of the version of the API used to produce the Excel file, which I assume Marco keep low enough to be compatible with the maximum number of people. Going too high would cause issue to people with older version.

 

[Jason McCleskey]

Agreed. It seems to be related to OneDrive trying to sync the file and not liking something. If I set it to export to a non-OneDrive directory there is of course no banner message at that point. Then if in Windows Explorer I copy the file over to a OneDrive directory it still shows up. So it's not even related to it being opened up "live" by PSD. There is something OneDrive doesn't like about the way the Excel file is formatted (probably due to older api as you note). But since it works fine from an Excel standpoint that's a OneDrive bug - not a PSD problem.

No need (in my opinion) for PSD to be able to upload to OneDrive directly. I'll just consider this a OneDrive issue and use the copy/paste option.

Thanks all for the feedback.
Jason

 

[Duncan Wright]

My experience of this is that the xlsx files PSD is exporting can be fixed by disabling the "check compatibility when saving this document" tickbox in File / Info / Check for issues / Check compatibility. Unchecking this box enables the saving. Also, you can uncheck it at the time of saving.

This might give you a clue in fixing this

 

[Jason McCleskey]

Thanks Duncan. Unchecking the "Check compatibility when saving this workbook" in Excel does allow me to perform the save on my end as well. That's much better when exporting large datasets than the copy/paste option. Appreciate it! Problem resolved.