I work in Finance at my company and we always save revised copies for Excel files instead of saving over.
But we also have strict rules on it. File name is always “xxxx_Workbook Template Name_MMDDYY.xlsx” or “_YYYY_MM.xlsx”, depending on how often it gets updated.
Older versions get moved to a subfolder. It helps us go back and find out what something was if there was a mistake or revert back if Excel done fucks up.
It never works when you need it. Like “that file was too big”, that file was on a network share, that file is outside the window of how many old changes are saved. It’s like using an undelete utility. Sometimes you get lucky.
It’s better to save every change as a dated/numbered file or use a real source control system.
I work in Finance at my company and we always save revised copies for Excel files instead of saving over.
But we also have strict rules on it. File name is always “xxxx_Workbook Template Name_MMDDYY.xlsx” or “_YYYY_MM.xlsx”, depending on how often it gets updated.
Older versions get moved to a subfolder. It helps us go back and find out what something was if there was a mistake or revert back if Excel done fucks up.
Could just use git…
using git on a bunch of XML files saved into a binary ZIP file with a
.xlsxfilename extension is a hell whose circle we have not yet discoveredAlmost 24 hours and no one has commented on MMDDYY? I don’t know whether to be proud or disappointed.
As an European I just sigh and read on.
Do people in your company know that there’s something called Windows File History?
It never works when you need it. Like “that file was too big”, that file was on a network share, that file is outside the window of how many old changes are saved. It’s like using an undelete utility. Sometimes you get lucky.
It’s better to save every change as a dated/numbered file or use a real source control system.
If there’s “Windows” or “Microsoft” in its name, you’re risking your business by relying on it