Banded report writers, like in Access, FoxPro, Paradox and others, plus these drag and drop query designers, help end users stay in a productive relationship with their core concerns.
However, once a given database reaches a certain threshold maturity, in terms of numbers of users, its criticality to the enterprise, you generally want a more austere industrial scale engine.
Traditionally, those'd be relational, meaning tabular (rows and columns, like a spreadsheet). However, as Python's flagship ZODB makes obvious, your Model needn't go the relational route, like if networked object storage works better. Many European companies are ahead of the curve in this respect, but then it's not either/or.
OK, that's the "lecturer's version" of what I started babbling to Alexia about. I've also cc-d her some recent emails to Phyllis Shelton, Dawn's principal bookkeeping collaborator in the last couple of years.
Our DWA is still very much a small, nimble business, an "agile" as some say these days (which is what Python is too).
Alexia also mentioned something she'd heard on the radio about using fullerene (Fn) to boost solar panel technology. I mentioned my friend Ed's focus on its chemical naming.
