11–20 of 378 posts
I feel the same way about Access, too. It doesn't matter whether they're "real programming", it matters that they let real people solve real world problems for themselves, who otherwise would have to pay real programmers real money to develop real applications.
I feel the same way about Access, too. It doesn't matter whether they're "real programming", it matters that they let real people solve real world problems for themselves, who otherwise would have to pay real programmers real money to develop real applications.
https://www.youtube.com/watch?v=0nbkaYsR94c
It is amazing how rich the ecosystem is. I didn't know about pivot tables. Excel has always impressed me, and continues to do so the more I learn.
This is exactly why we're building https://glideapps.com !
A cell is simply a computational variable (as opposed to the notion of variables in lambda calculus). A named range is a data structure (a struct). The rest are term rewriting
This video by Joel Spolsky taught me a lot of new Excel tricks/QoL improvements: https://www.youtube.com/watch?v=0nbkaYsR94c It is amazing how rich the ecosystem is. I didn't know about pivot tables. Excel has always impressed me, and continues to do so the more I learn.
I feel the same way about Access, too. It doesn't matter whether they're "real programming", it matters that they let real people solve real world problems for themselves, who otherwise would have to pay real programmers real money to develop real applications.
You could damage the MDB a number of ways including:
- Leave Access running before shutdown (or power loss)
- Intermittent network outage to the file server
- Multiple users trying to access the same MDB (or anti-virus scans/locks, even on another user's machine)
- JET inconsistent versions / Access inconsistent versions / Patch Levels
The biggest headache though with Microsoft Access was never the product itself. It was that the product didn't really have a natural evolution. You'd start with a single MDB/single employee, but one day you'd need two employees or more (and security, and more tables, and this and that), and while you could migrate the MDB into a real database engine ($$$) and use Access as the front end, the record locking was funky and scaled poorly (plus control was limited).
The whole product felt a bit like a mouse-trap. A nice shiny piece of cheese, that genuinely tasted good/worked well, but as soon as you tried to move it SNAP. I don't dislike Access, but it was always painful when a business outgrew it (whereas Fortune 500 companies live and die on Excel).