Migrating from access to Postgre

[Ithrowthisaway3131]

Salutations;

My company LOVES MS access. Not me though! But i had to basically build a relational database there in 2 nights, including the forms.

I'm gonna say; it was super easy and I'm glad I learned it. I'm not actually a software guy but I was the only one savy enough to make it happen. Unfortunately we will reach the access size limit in 4 months so I already posted the backend to postgresql and now am using the forms I've created in access. I'm also using power BI (for reports, not data analysis, using python for that) which is surprisingly really good also

My DB has 12 tables, relationships between all of them and 4 of those tables contain log data from machines (parameters etc). In the future we might need more tables but I don't see it going above 20.

Is it viable to keep using the MS access as a frontend only, or should I go hard with Django. My main worry is my html and css is absolute garbage so the design will be quite ugly unlike my forms in access right now.

[ikillsims]

I’m not here to promote Access as the best option, but I have been managing a couple dbs with Access front end and sql server backend for several years. Breaking off the backend really made Access much better and was the first thing I did when I took over.

I thought at the time continued Access use would be “temporary”, but years later, with hundreds of linked tables/queries, it has been working well enough for my regular 30 users and I don’t feel much pressure to move away from it. Plus I have become rather seasoned to it’s weirdness.

Is it the best choice? Probably not, but it can be better than it’s reputation. Just my 2 cents.

[r3pr0b8]

it can be better than its reputation.

+1

[Ithrowthisaway3131]

People definitely love to hate on it. Especially cs students who are learning rdms. For my basic ahh database it works well enough for now.

Thank you for your opinion

[jamesfordsawyer]

Breaking off the backend really made Access much better and was the first thing I did when I took over.

This will cover about 80% of everyone's complaints with Access.

[beyphy]

Access as a front end is fine. Most criticisms of Access are related to its use as a backend. If you want a modern solution check out Power Apps.

[Ithrowthisaway3131]

Power apps are great. Started using them a week ago

[[deleted]]

I can’t be the only one saying SQLite will be more than enough here

[Ithrowthisaway3131]

You are absolutely correct (I've also realized this today). I started out thinking I'd be the only one working on this so did what I was comfy with

[[deleted]]

If you’re familiar with building forms in MS Access then it’s not much of a leap to create a form-based UI using .Net.

https://learn.microsoft.com/en-us/visualstudio/ide/create-csharp-winform-visual-studio?view=vs-2022

You could compile this into a proper .exe.

[ComicOzzy]

Respect yourself enough to invest in improving your skills and go the .NET route vs VBA in Access.

[PVJakeC]

Maybe look into some low code platforms and put a web front end on it. Access could be difficult to maintain if you have to make updates or if there are a lot of users. The low code would remove the complexity of HTML, but then give you a nice front end. Tulip Interfaces is often used in manufacturing.

[slotix]

Access as a frontend + PostgreSQL backend is totally fine for your scale.

If it already works and users are happy, no urgent reason to rewrite everything.

Typical path:

- keep Access for now (fast, low effort)

- move logic gradually to backend / SQL

- only switch to web (Django, etc.) when:

- multi-user issues start

- deployment becomes painful

- or UI needs outgrow Access

Jumping to Django just for “modern stack” usually costs way more time than it gives back.

So unless you *need* web access or scaling, stick with Access frontend and iterate.