Right now all we have is desktop Access. Which I'm deeply mistrustful of by reputation. So the actual question is - what's likely to go wrong if I do?
An Access DB is made up of two parts: The front-end (forms etc) and the data store which is a file that's accessed via ODBC, with the Microsoft Jet driver.
Once you've got it working in access, you can swap out the Jet DB for a SQL Server connection. I've never needed to do this, but I've heard it can be less painful than migrating from Py+SQLite to Py+MySQL, since Jet behaves more like a conventional db.
Then while it's running in MS SQL server with your Access front-end, build the strategic front end in something else.
So the official answer from our Data/Analytics dept was 'have you considered using Jira?'. I suppose it does implement a way of setting up one:many relationships...
Praise be.
An Access DB is made up of two parts: The front-end (forms etc) and the data store which is a file that's accessed via ODBC, with the Microsoft Jet driver.
Once you've got it working in access, you can swap out the Jet DB for a SQL Server connection. I've never needed to do this, but I've heard it can be less painful than migrating from Py+SQLite to Py+MySQL, since Jet behaves more like a conventional db.
Then while it's running in MS SQL server with your Access front-end, build the strategic front end in something else.