
If you DON'T use a live connection to your data, you are then storing all of that data in a PBIX file (thus NOT eliminating Problem 3), and your data will need to be updated in order to keep your reports "fresh". If you are doing a lot of analytics/reporting on your data, PowerBI using a live connection may be a good choice (but its definitely not an ad hoc query tool - and wont eliminate Problem 1). Also, if the data is stored in SQL Server, and it is accessed using Windows authentication, then Problem 2 is a myth. There is not a need to migrate to some other tool to fill that purpose. there really is no substitute for what MSAccess can do. MDB/.ACCDB file to LINK to data sources so you can see it or do ad hoc queries with it (Usage 2). Then SQL Server, or Azure SQL will take you to all ends you wish to travel to! Again, SQL Server Express is a good first step.

It does fine for small businesses, many small business can work just fine within the constraints of security and size that the JET/ACE format limits us too, but once your needs go beyond those limitations, or you just need a standard repository to use across your company, the JET/ACE (Access) format should be migrated away from. The Access (aka: JET or ACE repository format) is not a up to par for corporate data.

MDB/.ACCDB file format as a repository to store company info (Usage 1 and Problem 2 & 3), then don't! Use SQL Server. (this is not an MS Access issue by the way)ģ) Too many silos of data (ie: corporate data in stored on Jacks or Jills PC and they went up a hill for vacation). The common problems being sought to fix are:ġ) People are creating inefficient queries against data they don't understand. MDB/.ACCDB format as a data respository)Ģ) Access to data (not the application, but gain visibility to data that is stored in a non-MSAccess repository)ģ) As UI to data (Forms, Reports, or Queries against data from all sorts of repositories)

I hear people / companies say they are migrating away from Access I often ask what they are using Access for, and what problem are they trying to solve by eliminating it from their environment.ġ) Store Data (ie: using the.
