Excel is fine for warehousing, but it's not super easy to navigate without tons of way too complex macros and you can't have multiple edit sessions on one file.
I'd just use like a Postgres instance with something like Metabase for active tracking of part status with some basic CRUD scripts set up to buttons on dashboards for each car section or something.
Maybe a Wekan or something for active tracking of part production and general activity stuff.
Excel is fine for warehousing, but it's not super easy to navigate without tons of way too complex macros and you can't have multiple edit sessions on one file.
I'd just use like a Postgres instance with something like Metabase for active tracking of part status with some basic CRUD scripts set up to buttons on dashboards for each car section or something.
Maybe a Wekan or something for active tracking of part production and general activity stuff.
I'm of the mind that if the thing you're doing is too large or complicated to use Excel, then it doesn't need doing.
Too many parts and systems in your car for excel to be navigable? Car needs fewer parts and systems.
Too many guys in your military to fit on an excel sheet? Your military needs to be smaller.
Excel has a limit of 1,048,576 rows while the army has "1,073,200 total uniformed personnel" according to Wikipedia, time to start decimating.
I'm sure you can just consolidate all the people called Mike into a single guy with the "Duplicate Entry" function.
this is why there were centurions
Yet you comment here.
Do you mean to tell me there's a way to post here other than using an excel script?
Nvim is always an option