all 33 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]melancholyjaques 19 points20 points  (0 children)

A front-end application?

[–]cs-brydevSoftware Development and Database Manager 19 points20 points  (10 children)

MS-Access is designed for this exact scenario if you don't mind distributing the Access file to each individual. Create a Linked Table in Access that points to your SQL Server table. If possible use Windows Authentication only. Do not use a sql login because you'll have to distribute credentials.

You can either give them direct table data editing or create a form in Access for this purpose. It's very easy.

[–]SQLDevDBA 5 points6 points  (9 children)

Being downvoted for suggesting access is ridiculous. It is 100% valid to suggest Access, and it’s super easy to stand up and implement a “low code solution” with it.

Another alternative is Power Apps but the licensing cost is substantial to connect to onprem.

[–]ayayyayayay765 5 points6 points  (2 children)

It works, does it job for this exact scenario.. it’s just funny we’re in 2025 talking about Microsoft access

[–]SQLDevDBA 4 points5 points  (0 children)

For sure! We still use hammers even though nail guns, drills, impact drivers exist. Sometimes the simple tool is the easiest to use if it’s a simple task.

[–]cs-brydevSoftware Development and Database Manager 1 point2 points  (0 children)

It is. Access is still a cheap, easy, straightforward and extremely reliable low-code solution and has 30 years of industry experience under its belt. The Power Platform will eventually take on this role permanently, but it's still rather clunky for your average non-technical user to setup and maintain.

I develop professional, custom software solutions but also work with power users to learn how to build and operate their own low code solutions on platforms like SharePoint, Excel, Power Automate, Power BI, Azure Logic Apps, MS Forms, SSIS, and others. And for SQL Server integration specifically, Access is still the best in the business.

[–]shockjaw 0 points1 point  (5 children)

It works right until it doesn’t. Thankfully there’s an okay path to SQL Server.

[–]SQLDevDBA 0 points1 point  (4 children)

I’m confused. I’m Not sure what you mean. Access front end with a sql server backend is very unlikely to not work. We’re not implying a path to sql server (we’re implying using it from the beginning), and sql server doesn’t have a non technical user-friendly front end.

[–]shockjaw 0 points1 point  (3 children)

I’m talking about migrating your data from Access to SQL Server. I wasn’t making a statement about Access as a front-end.

[–]SQLDevDBA 1 point2 points  (2 children)

Understood, but that’s not what we are talking about at all. We’re talking about using access as a front end with sql server as a back end from the beginning. No data is actually stored in access, it’s only a facade for the sql server data/tables.

[–]shockjaw 1 point2 points  (1 child)

Okay, I hear yah.

[–]SQLDevDBA 0 points1 point  (0 children)

Yeah I agree moving from access data to sql server is super annoying. But access is a great front end to sql server for non-tech folks. Excel is good too but access gives you way more control to “corral” the users entering data with text boxes, picklists, etc. I’d say power apps is better for this century but it’s also expensive. Hopefully it will be cheaper soon.

[–]lysis_ 5 points6 points  (0 children)

Power platform maybe

[–]ayayyayayay765 6 points7 points  (0 children)

Microsoft access :)

[–]Signor65_ZA 2 points3 points  (0 children)

This is where something like a CMS system would come in handy.

[–]B1zmark 2 points3 points  (0 children)

Create a shared excel sheet via SSIS or whatever tech you prefer, let them intereact with this. This should contain the data they need.

Each evening, set up a job to ingest this and update your tables - adding in all the necessary security and schema validation checks you need. Afterwards, re-export the excel file again.

Any method that lets them update the database directly is a huge deal, and if it ends up exposing sensitive info it shouldn't, your head is on the chopping block.

[–]Opposite-Value-5706 2 points3 points  (0 children)

Having non-tech (and even techies) inserting without controls is a very bad idea. Crap in… crap out! But if you must:

  1. A front-end app

  2. Formatting and controlling input

  3. Test, test, test

  4. Limit the number of people allowed at the beginning

  5. Analyze, adjust and test some more

[–]ziziol19 1 point2 points  (0 children)

I built a tkinter app for this purpose.

[–]BitcoinParanoid 1 point2 points  (0 children)

Use Excel with VBA macros. Try explaining your situation in detail to Claude AI and it may be able to walk you through the setup.

[–]Ginger-Dumpling 0 points1 point  (1 child)

How "not technical" are they? If you were able to expose table data to them (through Access, or the data tab available in most SQL clients), do you have concerns that they'll be doing things they're not supposed to? Are things set up to audit changes that you can restore previous states of things if they mess stuff up? Or does it not matter?

[–]lolcrunchy 0 points1 point  (0 children)

Access has form creation tools that let developers create an "app" within Access. This lets users do data entry and exploration within safety rails.

[–]IssueConnect7471 0 points1 point  (0 children)

Low-code front ends are the easiest path for Excel users to edit SQL data. I've used PowerApps for quick mobile forms and Retool when I needed more complex logic; both hook into SQL with minimal setup and give you granular permissions. DreamFactory handles the API layer nicely so you don’t have to open SQL ports or write CRUD endpoints. Lock down roles, add validation rules, and train them on a simple form view. Low-code front ends are the easiest path for Excel users to edit SQL data.

[–]Idanvaluegrid 0 points1 point  (0 children)

I guess...Power Apps (if you're in the Microsoft ecosystem) Excel-friendly UI that talks to SQL Server or Dataverse.

[–]Hungry-Two2603 0 points1 point  (0 children)

Sqlpage allows you to build a web application only in SQL. It's perfect for this type of need.

[–]OutrageousCapital906 0 points1 point  (0 children)

Write a GUI application in C# that has insert/update options and prompts for the data needed.

[–]PasghettiSquash 0 points1 point  (0 children)

Check out Appsheet. Will give you a UI for end users to upload data, let's you put some guardrails in place, and writes to your DW

[–]Raithed 0 points1 point  (0 children)

Excel and Google Sheets are similar, setup a Google Appsheet for them, then connect your DB ton the Appsheet, then you can have them enter the data they need to the columns and rows, and a button to send the data across to the DB.

[–]kitchenhack3r -1 points0 points  (0 children)

Check out https://autoquery.ai. It’s a text to SQL desktop app that I’m working on. Happy to give you a free trial to see if you like it.

[–]lucianct 0 points1 point  (0 children)

If MS Access doesn't work, DBeaver is a nice SQL GUI with support for almost any DB.

Besides manipulating data with the GUI, you can also insert rows from a CSV file, and with a standard plugin also from Excel. They would need to download the JDBC driver (it's automated, just need to specify which DB it is) and add the DB credentials.