> allow 2 of my coworkers in my office (on my network) to access and use a database I will build?
Do they have to only read information from the database? Or will they also have to enter/change/update any data?
​
Access sucks as a backend but can be a decent front end.
​
Do you need the solution to be web-based? if so, https://dbfront.com/ might work for you.
​
The thing to bear in mind if you want to develop a bespoke tool is: who will mantain it? You can get a developer to build something for you fairly easily, but rest assured that requirements will change over time, people will want tweaks etc. Do you have an in-house developer? If not, a solution which requires minimal coding and which can be managed by the existing employees would probably be better - be it Access, Dbfront or else.
The fact that most corporate users don't realise that Excel is NOT a database must be one of the top reasons for screw ups in the business world!
​
Does a database already exist for this?
How much data will the users input at a time?
How many users will access and modify the data at the same time?
​
For simple projects where users mostly enter one row at a time, an Access front end linked to a SQL Server (or equivalent) back end can be a good solution. Access sucks as a front end but isn't too bad as a very simple front end.
​
Or you could think of a web-based tool like dbfront https://dbfront.com/
​
If users expect to be able to enter multiple rows at a time (eg they need to copy hundreds of rows from elsewhere at the same time) then I'm not sure.