5 ms·
Am I the only one here who remembers MS Access? It was a great no-code/low code product that created silos of information in many organizations and it was a rea
by JamesAdir 5y ago
Am I the only one here who remembers MS Access? It was a great no-code/low code product that created silos of information in many organizations and it was a real PITA to transfer it to other technologies.
The advantage in MS Access was that it was part of the MS ecosystem and used VBA which is well documented. What will happen when you'll want to transfer something you've made in today no-code solutions to another platform?
- collaborative 5y agoMS Access was indeed great. It was really simple to publish a site in the early days of asp that made use of it as a data source Performance-wise sqlite probably wins, but Access had the added bonus of an extremely straight-forward UI
- forinti 5y agoI've seen this in different organisations: an accountant writes an MS Access app and when he cannot handle it anymore, he hands it over to IT (which is always so slow to provide solutions because they keep worrying about security, interoperability, consistency, and such). One such app had in all its tables a column called "useless". It turns out it was the primary key. The author didn't know what it was for and didn't figure out from its name that it was important. There were also foreign keys referring to the description columns, not the primary key column (which was useless, after all). In one instance, I saw an IT manager being asked for support for an app he had never heard of. It was another attack of the coding accountant! I call it code and run.
- chazu 5y agoNewer solutions which use abstraction layers like postgREST will hopefully result in easier migration down the road - but I doubt most products/projects use such a thing.