And then OneDrive comes along, someone accidentally saved “to the cloud” (IE the default windows location of OneDrive). And of course someone (you) has to fix all the desync bullshit.
Fuck excel, fuck Microsoft, fuck OneDrive!
Thank god my company is transitioning to a decent no code solution (nocobase plus literally anything that can interact with postgres - currently n8n but not yet limited to that. It’s a transition from excel, literally anything is better! (Tho, nocobase is awesome, non has it’s perks)).
Many parentheses, soz.
Fuck excel, use a database!
I’ve seen that. Used for customer service history AND planning with 3-digit week numbers (the first digit is the last digit of the year) and a lot of macros. Guess who had to fix the macros in 2020 without changing the idiotic 3-digit week numbers?
15000 rows. 120 columns. One sheet. Creation date: 2011. A dedicated computer. Working at a multinational company is bad for mental health.
100k+ rows and columns that want over ‘BMW’, worked actually fine
And then OneDrive comes along, someone accidentally saved “to the cloud” (IE the default windows location of OneDrive). And of course someone (you) has to fix all the desync bullshit.
Fuck excel, fuck Microsoft, fuck OneDrive!
Thank god my company is transitioning to a decent no code solution (nocobase plus literally anything that can interact with postgres - currently n8n but not yet limited to that. It’s a transition from excel, literally anything is better! (Tho, nocobase is awesome, non has it’s perks)).
Many parentheses, soz.
Fuck excel, use a database!
I’ve seen that. Used for customer service history AND planning with 3-digit week numbers (the first digit is the last digit of the year) and a lot of macros. Guess who had to fix the macros in 2020 without changing the idiotic 3-digit week numbers?
FiServ. Distributed to clients.