Would Anyone be Interested in a Vehicles 3rd Ed Workbook?

[Bruno]

Originally Posted by panton41

...come back when your HR department is based entirely on a kludged up Excel sheet someone whipped up a decade ago and people just keep passing around and IT only discovers this when the latest version of Excel breaks it.

For Reasons, I got stuck maintaining my company's billing system, which was written in Quatro Pro. There was a memory leak in our Quatro Pro version (which was decrepit), so the script had to save it's state, stop itself, and then restart itself, every 20 clients or so.

It was... not nice. No. Don't go there.

Originally Posted by panton41

Once you start digging into GVB you'll realize under the hood it's actually a specialized relational database.

I'll third GVB. I'm quite satisfied with it.

A spreadsheet is an interesting rapid application development environment, and it's fundamentally a functional programming environment rather than a procedural or object oriented one. But it's not feature complete. It can't do loops of an unspecified length, for instance, and all branches of every conditional have to be completely executed whether they're used or not. Which is just... no. There's too many switches and toggles in the vehicle design process.

But they do work fine as a bespoke solution for each design - trying to make your mech work and fiddling around with the numbers until the legs don't fall off but not changing any fundamental design parameters - works great. The more generic you get, the more contorted it gets.