At the end I’ve lost all info relating to Customer A, and each file I’ve saved actually has details for the next customer with the last customer’s details actually being in two files with different names. I then save as Customer B Outstanding Invoices and repeat for Customer C. I then refresh for Customer B but in doing so it overwrites the file “Customer A Outstanding Invoices” with Customer B’s details and data. I “refresh” it for Customer A and Save As “Customer A Outstanding Invoices” – it turns AutoSave on. Say I have a file called “Customer Outstanding Invoices” and have AutoSave off.

This when mixed with AutoSave and Save As can mean huge problems. I use something called Jet Reports which automatically updates spreadsheet templates with live data from our ERP system, taking into account user-specified parameters. If you don’t click “save”, you obviously didn’t want to keep all that work, did you? All they’d be doing is applying their needs to your problem. Some users want to be able to edit data then abandon what they’ve typed for a safely-saved version. This would baffle the designer of this feature, because they can only see their own point of view to the exclusion of all others.ĭear developers: if you’re still having trouble understanding what is so annoying about this feature, just imagine that users had a feature to delete your code every time you switched off your PC. But this article describes the many, many scenarios when that assumption doesn’t hold true. If you come from the assumption that you’d never want to lose any data you typed, it would make sense. Because you will invariably find those decisions come from your own blinkered viewpoint. Provide options, don’t try and make decisions for users. Every time you make a decision for the user, you fail them. Forced Autosave For Everybody is one of those features that I can only image came about because they let one of the more Aspie-prone developers run wild.

Mac turn off autosave for an app