Ask HN: Why isn't there a modern MS Access clone?

115 points by Norther ↗ HN
HN, this is something that I've always been interested in: Why isn't there a modern piece of software akin to Microsoft’s Access? I know there are plenty of issues in scaling these kind of systems, and that these kind of platforms can feel clunky and unwieldy but I still find it surprising that there isn’t a simple platform for creating CRUD apps. It doesn’t seem like an unachievable goal to me: you need the ability to create forms, design database tables, manage user permissions, manage data workflow (ie: send an sms if <condition>, seek approval from <user role> for <action>), and view/search data. I’m certain these features would be useful for all kinds of business scenarios where building, maintaining, and hosting a custom solution isn’t worthwhile, or would be unideal compared to using a standardised tool. Are there tools in this space that I’m missing? If not, why isn’t this being pursued? Eagerly looking forward to your thoughts.

113 comments

[ 60.5 ms ] story [ 2616 ms ] thread
Did you take a look at Libre Office Base [1]? It seems similar to MS Access, though I haven't used it.

[1] http://www.libreoffice.org/discover/base/

Interesting! I was thinking more along the lines of a web application, but it's nice to see an (actively maintained/developed?) somewhat-literal clone of Access.
MS Access is just a FileMaker clone, and FileMaker is still going strong, so I fail to see the problem.
FileMaker seems to have a web based solution too.
Maybe because writing an Access database still requires a programmer, and you can get better value by hiring a PHP programmer to write two pages and three tables.
Yep, this is what always happens with these types of applications. There was a whole slew of these type of tools in the 90s dubbed '4GL' with the idea they were a level above traditional programming (3GL) where business people could drag &drop their way to a new app.

It was a disaster and none of those 4GLs are around anymore. There is no interface that's as easy as sending an email to a developer saying "I need an app that does this..."

They are around though. I did a job at a company that had a 4GL app used by business analysts to generate the APIs, UI and business logic to be used for e.g. mortgage calculations on websites.
(comment deleted)
I think you are right. For soft applications, Excel is a powerful enough database that non-programmers can use. Anything Excel can't do can be done 'easily' by mysql.

I know that I've sat down to learn access (and later LibreOffice Base) but by the time I start into it I just think "there's really no advantage to using this over just mysql and a web page front end" and stop learning.

I'd say that the "new Access" is WordPress or Drupal. They're often used in much the same way - create a bunch of entity types that automatically connect with forms and views.
The thing is though, you actually require a server and apache etc for the PHP example.

For a front office/business person who doesn't do IT as a full time job but has a reasonable grasp of technology, they can create something "good enough" quite easily, without having to go through the whole Corporate IT process.

This is also why Corporate IT doesn't like the Front Office getting Access, as they still ask for support when their home-brew app goes wrong.

> Corporate IT doesn't like the Front Office getting Access, as they still ask for support when their home-brew app goes wrong.

The Access contraption then gets an ODBC backend to a proper database. Then parts of the Access Visual Basic spaghetti get ported to PHP. Other parts get ported to JSP. It ends up getting entirely ported - but for lack of budget for a full rewrite, the previously developed JSP parts are preserved. The whole thing doesn't take advantage of contemporary UI patterns because it closely matches the design of the original Access database. I'll spare you all the episodes of crippling slowness and the data corruption catastrophes that triggered each improvement increment.

On the other hand, the users managed to build themselves a serviceable tool when the IT wouldn't even speak to them without a ten-months project - and then they foisted it upon IT... From their point of view the ugly ten-years journey has been a success !

Anyone that has ever done, say, a Windows or Office upgrade for a large corporate knows the pain of cataloging all the End User Apps.
Oh yes - I forgot to mention the schlepping of VBS code across two Microsoft Office upgrades during the application's lifetime... And the migration exemptions that last for years while the porting is done - lots of love from the desktop IT department to this application...
Likely correct. I'm part of a grant writing firm (http://www.seliger.com) and in the '90s and early 2000s we ran tons of stuff on Access. Now almost everything we did then runs on Highrise, Constant Contact / Mail Chimp, and the like. Basically, everything we did became a web app that works better and is easier (at least for us) to use.
FileMaker Pro has been around forever and is still supported with new versions as far as I know.
Not that searching is difficult but I'll put the link here anyway: http://www.filemaker.com/products/

1) I didn't know that Filemaker was still around.

2) I didn't know that it is an Apple subsidiary.

3) Pity there's no Linux version, I'd use LibreOffice Base if you're in Linux as someone else here has pointed out.

That's incredible - I remember FileMaker from the 1980s. Look at the functionality of that app and the great design of the site! If that were a startup run by a bunch of hip Millennials out of San Francisco, it'd be worth a couple billion dollars, easily. (Instead we get one-off, single purpose hosted apps like Trello, and FileMaker languishes in obscurity.)
It is incredible, isn't it? You have become more cynical with old age like myself – but I think there is some truth to what you're saying.
This brings back incredibly relevant memories: my first paid job back in 2002-2003 was maintaining an old Filemaker database and related forms.

I ended up doing an Access database and created a few forms on top of it, including automation for automatically exporting order forms as Word documents. There were a few gotchas in writing VBA but overall the process was easy to pick up and be productive quickly.

I worked on a port of a filemaker database once. During this port but well before the end there was a power outage in the office and the discovered that the filemaker server had entered some sort of silent failure mode where it appeared to be working on the outside but wasn't writing anything to disk. It operated like this for months...
Although not an exact replacement to Ms Access the types of products marketed by big tech to "technical BA's" appeal to that requirement.

Building apps with clicks not code is the utopia these people are seeking, so the vendors will do everything they can to appeal to that.

There are literally heaps in this category, but one that really started it all is Salesforce and their force.com product, they are selling the dream like no-one else.

More frequently coming up now is MS PowerApps and MS Flow coupled with either SharePoint lists or Microsoft's Common Data Service because they are included for free in the Enterprise Office 365 SKUs.

Dynamics 365 offers a lot in this space but is more pricey (the $10 team license is good value though). Zoho Creator is another example too.

Yeah LibreOffice - Base! Take a look at My Visual Database, VFront, nuBuilder, Kexi, Brilliant Database, MyTaskHelper and many many more. Each of them has different uses and there are web technologies as well.
There are quite a few products that attempt to be a web based equivalent of Access.

The two that seem to be the closest to me are Google's AppMaker (https://developers.google.com/appmaker/) and Bubble.is (https://bubble.is/). I call these two out because they both allow for coding when the "default path" runs into a wall, and both include more than just forms and tables. However, they both still have warts. Appmaker, for example, has a pricing model problem. It's $10/user (GSuite), so you can't use it to build anything that involves casual outside users, like an employment applicant tracking system.

The next tier down are somewhat similar products that have been around longer. Like Quickbase (http://www.quickbase.com/), Caspio (https://www.caspio.com/), Airtable (https://airtable.com/), Zoho Creator (https://www.zoho.com/creator/), Rajic (https://www.ragic.com/), and Knack (https://www.knack.com/). These all work great if the app you're making fits into their somewhat fixed view of the world, but hit a hard wall if it doesn't. Some of them also have the same pricing model problem I mentioned in the preceding paragraph.

The one I really thought was going to emerge as the market leader was DabbleDB. Sadly, Twitter acquihired them and shut it down. Here's one of the demo videos: https://www.youtube.com/watch?v=6wZmYMWKLkY It was very ahead of it's time back in 2007.

Dabble was pretty neat, and it was written in Smalltalk, too. I think each user got their own Smalltalk image, and their data was saved directly to the image.

I can't remember if I learned that in a video or a post somewhere by Avi Bryant, though. I was really interested in Smalltalk in 2009/2010 and I remember seeing Dabble DB coming up a lot.

I'm sort of surprised LibreOffice hasn't tried to fill this gap, it would be a nice way for them to earn some income if they do it just right enough. I say this because Open Source projects need to be funded some way, somehow.
You mean with a web based database? I thought LibreOffice did have a local Access equivalent called "Base".
It's not that great of an experience out of the box. Non-tech savvy users can make use of MS Access.
LibreOffice Base (http://www.libreoffice.org/discover/base/) fills the gap. It's a combination Access-like local database as well as a ODBC/JDBC client.
LibreOffice suffers from it's terrible scripting language. Compared to VBA it is wordy, non-obvious, and in general a royal PITA to work with.
You missed somehow 3 the most powerfull alternatives, Outsystems, Filemaker and Oracle Apex.
My list is products that were web based, offered as a service, and with up front pricing. That said, I'm sure I missed others as well.
Not an MS Access clone, but a good 4GL easy database tool I like is called DataFlex [0]

Very easy to use and you can create basic applications without additional programming. Although of course it helps if you know how-to write code.

There's an embedded database that you can use out of the box. But you can also use any of the main SQL Database engines.

For building commercial applications you have to buy a developers license.

For building your own non commercial applications you can use their free personal license. [1]

Disclaimer: I use the language professionally and run an open source website that has free tools and code examples in DataFlex.

[0] http://www.dataaccess.com

[1] https://www.dataaccess.com/Resources/Licensing/DataFlex-Pers...

That's crazy, I used DataFlex briefly over 30 years ago.

Had no idea it was still going.

Yep, but it has changed quite a bit since then.

30 years ago there was only console mode, albeit in different flavors (unix/DOS). Nowadays the main product is Windows oriented and also has a Web offering. You can still buy a console mode linux version, but it hasn't had updates in over a decade. Yes it runs and works on recent Linux versions, no I would not recommend spending any money on that.

Your 30 years old data files however could still be read. You might need to migrate it to a newer format if you want to extend and change things, but it would still work.

One of the things several colleagues have said to me over the years is that Access tended to be a dangerous tool in a large organisation: like Excel but on crack.

You end up with a large number of autonomous, undocumented systems built on an ad-hoc basis by personnel who were often not even in a technical role.

Personally I think that sounds like a great way to leverage the domain expertise of lots of different employees...but I guess it can become unwieldy. I know I saw some amazing things built with Access back in the day...

but none if it is easily integrated. you get a lot of data silos. don't get me wrong SQL server has that issue to. a lot of department apps that don't work well easily.
Over here we call those "clandestine Data Centers".
You also end up with a mess of VBScript code that isn't versioned. When something breaks and someone calls IT, it really helps if IT knows the system exists.

In a large organization, supporting disjointed business processes (or worse, fragile amateurish integrations) costs more than the software. At scale, consistency matters more than performance variance in some areas.

Access is also a nightmare from a security standpoint. AFAIK that's why it was abandoned; there was no way to keep the functionality and easy defaults that users liked while making it secure. It scares companies shitless to have critical financial data sitting in Access databases...

Yeah, but these things exist because they started as experiments which did not warrant getting a team of developers to burn through a million dollars for the first version.

Its really hard to know, in advance, which internal applications are worthy of a development team. As for nightmares... there's plenty to go around for everyone. Some of the worst nightmares are created by large teams of highly paid and skilled developers.

> Some of the worst nightmares are created by large teams of highly paid and skilled developers.

Sticking that above my desk

>You also end up with a mess of VBScript code that isn't versioned. When something breaks and someone calls IT, it really helps if IT knows the system exists.

This is one reason why (I guess) largish companies even have or create apps to manage other apps - like an app to manage (as in know about, not really manage as in monitor) all the other apps in the company. Like a list of apps app. Initially I wondered whether it was overkill but later realized that at that scale, such automation can be useful. But I guess it can go to the other extreme too and become a time sink.

(comment deleted)
I used to work at JPMorgan. We had an official acronym for these tools... UDTs, or User Developed Tools.

They initially started when ops teams were told a custom report for a client would be too expensive/slow to build properly by tech, so they would DIY a report in excel.

These started to get out of hand, and after a few years they numbered in thousands and had evolved from excel sheets with macros into full fledged Access DBs with ODBC connections into our data warehouse. A specialist team was created in Ops to build and support ever more complex UDTs, they were called the UDT Team.

Problem was that these were poorly documented and often done without consultation with Tech, so we would unknowingly break loads of downstream stuff whenever we embarked on new projects of our own.

Fun times. Plenty of stories.

We have created something that combines form builder, process flows, and if-then trigger rules at taskputty.com - we market it as a "build your own CRM system" but any crud or data flow style app should be doable.

We value as much feedback as possible. Single user is free, and we are completely flexible on price - we just would like to see more people using it.

It is loosely inspired by Trello.

In addition to everyone's replacement suggestions, I feel like it's worth noting that Access still exists and is part of some Office365 distributions.

For small-ish companies that aren't very technical, I would think the Office suite still has a strong attach rate. Regardless of whether or not Access is the best tool for the job, inertia is powerful.

Borland Delphi was the modern MS Access clone. Ever have seen how fast you can build an DB app with that? I'm sure the newest version of Delphi is still as good today as the 2001/2003 version at that time ;) On Mac it is Filemaker or not?
Pricing killed Borland/Delphi. Unattainable to regular developers and small businesses.
What about Lazarus?
Agreed. They finally have an "express" version but even that was $199. I'm sorry but I'm not going to pay that much money for something that I may never even use, especially for a stripped down version of it.
The advent of VB (and ultimately .NET) obsoleted the advantages. In modern .NET (and VB since 1998), you can pull a DataGrid onto the canvas, configure the DB parameters in the IDE and are basically done for an intranet data entry UI.
Filemaker has many issues: It's not an RDB, it's SQL support is limited to poor, and it's scripting is not nearly as versatile as Access.
Delphi was more of a VB competitor, Borland did have a database product called Paradox which was closer to Access.
fieldbook.com seems to check a lot of your boxes.

it has plenty of rough edges but has a solid relational model and is fun to use.

my only complaint is that api access is really expensive (making it cost-prohibitive to most HN readers) but the main product is cheap/free.

Fieldbook co-founder here, thanks for the mention. If anyone has a particular need for lots of API calls, message us and we might be able to work something out!
That's great to hear, I'll follow up via email.

Great product.

I came across this one recently:

http://www.matssoft.com/product/

Doing well in the enterprise sector in the UK. Recently acquired, though for relative peanuts:

https://www.youinvest.co.uk/articles/stockmarketwire/123954/...

Then again, I tend to be very skeptical of such tools, having seen them in action in the 00s, where they were very poor as a medium/long-term solution that ultimately hindered, not helped.

Looks interesting, but no pricing..."call for demo". Ugh, hate that.
4th Dimension (4D): http://www.4d.com

Started as a Mac only RDB in the '80s. Now runs on Mac and Win, as a single user, from a server, or can be compiled as a standalone app. Rich development environment, includes web server, PHP, SQL and a lot more. There is a small but vibrant community of developers but is accessible to anyone with some technical experience.

I think a lot of the common use case for things like Access were in storing customer databases - I'd imagine that a lot of applications that previously would have been done in Access are now done in CRM platforms like Salesforce - either because Salesforce and / or partner tools directly provide the functionality, or because you can go a pretty long way defining custom objects and fields.
i am workibg on exactly this, but not just an access clone but DDD point and click for the web. Any suggestions?
There are thousands (tens of thousands) of ERP/CRM systems that include an Access clone as a subset.