As the author points out, Access fills an interesting niche where Excel isn't quite enough, but a SQL database and all the stuff that goes along with it is way too much. On top of that, it's completely local so you don't have to pay for licenses or worry about data policies. That niche is big enough to sustain Access pretty much indefinitely. I think the lesson here is that business users more often than not want som…
I'm not clear on why you are referring to Access as an alternative to a "SQL based application". Access's SQL dialect is extremely annoying sometimes, but using SQL is a very significant (if not the most) reason for utilizing it rather than Excel. I went around and around trying to find a way to query Excel "tables" with SQL or something similar, but eventually gave up. There is something called DAX, but it seems dif…
Microsoft Access: The Database Software That Won't Die
211–220 of 365 posts
Re: Microsoft Access: The Database Software That Won't Die
#212Earlier quoted context omitted.
I wonder how much effort it would take to build a desktop application providing a similar user experience to Access, using SQLite.
Open/LibreOffice Base does have backends for MySQL and PostgreSQL already
Re: Microsoft Access: The Database Software That Won't Die
#213Is there a modern and/or open alternative to this? E.g a SQLite + electron or local web client thing where you could build a simple inventory or similar but you should also be able to scale it to client server when the need occurs 10 years down. Note that any number of cloud startups don’t count as an alternative to access. When these things start it’s as an excel sheet with data that no one will go through the enter…
Re: Microsoft Access: The Database Software That Won't Die
#214Literally worse than blogspot in every way.
Re: Microsoft Access: The Database Software That Won't Die
#215A number of years ago I was in the Navy and worked in an electronics shop on an aircraft carrier. We were responsible for calibrating and repairing all the test and measurement equipment for the entire ship as well as the squadrons that we carried with us. Easily over 10k individual pieces of equipment, each of which had to be calibrated on a specific schedule. Most of this data was managed centrally, and we sent/rec…
Being able to automate forms can absolutely revolutionize some businesses. Many business owners have no idea the extent to which automation is feasible here. I have seen fully manual paper process (printers/scanners/pen & ink/shredders/etc.) go into 100% digital realm and the impact it had on the business. It really is incredible the difference it makes. The most interesting factor was the fact that now that the inpu…
That's funny. I work at a very large fab, and of all the places I've worked, this is the one that's most in need of the sort of in-office hot path optimizations you mention, and doubly worse is that it's the least susceptible to allowing someone to do anything about it.
(In fact, it's regressing. This month saw a fab-wide rollout of a document management system that has caused a ~10x increase in wall clock time for attaching files to emails or through forms on the intranet. Now consider what that means when the company exhibits a pathological form of the passing-MS-Office-documents-around-to-each-other mindset...)
Re: Microsoft Access: The Database Software That Won't Die
#216Earlier quoted context omitted.
I was curious about ServiceNow and googled it and was excited as they offer demos. But they require registration and a lot of information about myself, so i stopped. Is it not meant for small businesses perhaps?
As a developer who is forced to use a service now interface for interacting with any other part of my organisation it's fucking awful in terms of user interface and friction. Unsure if that is because of our workplace setup or if it's intrinsic to the platform.
Which, as you might imagine, resulted in a huge number of multiple choice, similarly-named properties, with all options also being inscrutablely named.
Long story short: programmers are terrible at UX.
Re: Microsoft Access: The Database Software That Won't Die
#217Earlier quoted context omitted.
I wonder if sqlite could become this in the future.
I wonder how much effort it would take to build a desktop application providing a similar user experience to Access, using SQLite.
There’s a huge need for a sql-compatible sqite-like database for this purpose in Go.
Re: Microsoft Access: The Database Software That Won't Die
#218Earlier quoted context omitted.
I think Airtable is great, but it’s lack of aggregate functions really restricts it.
I certainly agree it's no replacement for a proper DB when full SQL functionality is needed, but it does have basic aggregates like count(), sum(), etc, available as formula fields: https://support.airtable.com/hc/en-us/articles/203255215-For...
Re: Microsoft Access: The Database Software That Won't Die
#219Earlier quoted context omitted.
Huh, similar story here. The nuclear department on my carrier needed to produce this monthly report for training hours that would take them a ton of manual effort. There was no budget at all for any kind of automation but Access was on every machine. I know what I'm doing with databases. I never want to use Access if I don't have to. But it has the enviable property of "no server administration required" which meant…
I wonder if sqlite could become this in the future.