3 ms·
SQLite. It's not close in terms of ease-of-use of the GUI administration and forms, but as a single-server database solution to embed into a line-of-business ap
by LeifCarrotson 3y ago
SQLite. It's not close in terms of ease-of-use of the GUI administration and forms, but as a single-server database solution to embed into a line-of-business app it's fantastic.
- afavour 3y agoThe GUI and forms is what made Access, though. Back in the day I actually made a system with Access that connected to a SQL Server database on the backend rather than Access's file-based engine. It's a real shame Access died, now there's no path from a spreadsheet to something more sensible.
- jkaplowitz 3y ago> It's a real shame Access died, now there's no path from a spreadsheet to something more sensible. Although it has certainly died in terms of mindshare, it's officially still supported for PC (not Mac): https://www.microsoft.com/en-us/microsoft-365/access https://www.microsoft.com/en-us/microsoft-365/access I actually have it installed right now, because it comes with Microsoft 365 Family, which I have on the Windows PC on which I'm typing this comment. I haven't used the modern version of it, though.
- chasil 3y ago...it's fantastic if you are able to live within its limitations, primarily being a single writer. If your application grows into the need for concurrent writes, then it will be time for another database.
- wild_egg 3y agoYou may be surprised at how far you need to grow to truly need concurrent writes. Blazing fast sequential writes is good enough for the vast majority of applications
- bonzini 3y agoI know how to write a Django app with a SQLite backend, but that's not what Access does. There are basic SQLite GUIs, but they have no reporting functionality and no customizable forms.
- eastern 3y agoThis is so true. A cross platform Access-like front-end that used sqlite as the data storage engine would conqueror large parts the territory.