@srtcd424 It was the lack of any kind of sensible concurrency control that I particularly remember. Two in-house apps could connect to an Access DB, while a third person was editing it directly in the app. And you'd get some behaviour, but good luck reasoning about what it was.
@david_chisnall I'm responsible for a few horrors that used Access over ODBC, definitely. Weirdly, the Jet engine itself in those days wasn't horrific - the closest thing to sqlite in that era.
@srtcd424 It was the lack of any kind of sensible concurrency control that I particularly remember. Two in-house apps could connect to an Access DB, while a third person was editing it directly in the app. And you'd get some behaviour, but good luck reasoning about what it was.
@david_chisnall oh, definitely, yeah. I mostly tended to create mildly cursed "intranet" apps that funnelled everything back to a single server, which mostly handled that.
@david_chisnall Also terrifying is spreadsheets "written" by people like accountants rather than professional software engineers. Like, even if it works, which version on which laptop is the "real" version which should be relied on for tracking a multi-million budget?
