it always interesting when multi billion dollar company's costing system is a 63 tab excel 97 spreadsheet at it's core...
it always interesting when multi billion dollar company's costing system is a 63 tab excel 97 spreadsheet at it's core...
You're viewing a single thread.
It will live in a folder with:
Spreadsheet(1).xls Spreadsheet - shortcut.lnk Spreadsheet(2) - Copy.xls New Spreadsheet - DO NOT USE.xls
I have colleagues who have 20 copies of the same document with slight variations named like this in a folder. I honestly don't understand how they function at work.
Sort by last modified
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 discovered
Almost 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
That's just version control but worse!
Could be they don't.
Every tech noob user I see. Worse if it's mac because 1) I cannot use it for the life of me and 2) almost every Mac user stores it in the same default downloads folder and won't know what path it's in unless they use the Finder tool.
It probably makes sense to them. I'm sure they're looking at your git workflow wondering how you function!
Nah, because when I ask them for info they stare at their directory and have to randomly open files for 20 minutes until they land on the item of interest...