Solid software for smaller, non-critical data sets
April 06, 2018
Solid software for smaller, non-critical data sets
Score 8 out of 10
Vetted Review
Verified User
Overall Satisfaction with Microsoft Access
Our users use Access to create forms that view and manipulate the smaller sets of data we keep. For example, rather than purchasing a full-fledged lab/test system, they created their own using Access. Other operations departments create the same types of content. There are many Access apps being used throughout our organization but they generally do not contain critical data.
- The interface is simple enough where entry-level users can build a way to consume the data they need without much effort or training. Advanced users can create fairly robust apps for their teams to use.
- The wizards are particularly easy for users to begin consuming data. In most cases, I don't have to get involved in developing Access applications unless they want specific data from one of our SQL databases that needs to be exposed.
- In addition to being self contained data stores, Access has the ability to read external data as well. In many cases, all I have to do is write a view in one of our SQL databases and users can get the data they need without me having to constantly write sql queries or design reports for them.
- Being that I also manage terabytes of actual SQL databases, I find that Access isn't great and accessing large amounts of data. Sometimes users ask for data sets that Access just doesn't deal with very well. I run in to performance issues and sometimes corruption issues with large data sets and complex apps.
- This one isn't really the fault of Access, but it's something to consider from an IT standpoint...as a DBA, I'm by default, spoken and unspoken, I'm expected to be responsible for the safety of all the data in our organization. That includes these Access apps that are so easy for users to create and then neglect to place in a location that gets backed up. I have been chastised for not being able to protect data that I didn't know existed. So if you have data that is critical to the business, even if it's a small but volatile data set, then you might want to consider a full-fledged database solution.
- It lacks the security features of more advanced database systems. Again, not a direct fault with Access, but users tend to feel they can put whatever data they want in these Access apps and don't pay attention to the fact that they could potentially expose data that doesn't need to be exposed.
- There was a period of time where we had a few users that created a large amount of Access apps. It quickly because difficult to maintain because I ended up spending so much time helping people with access rather than being able to focus on our centrally managed systems (ERP, Finance, etc)
- There are times when using Access to manage smaller sets prevents the organization from having to purchase unneeded software packages. It also allows users to answer some of their own data questions which saves me time. And saving my time adds value to the company.
- When critical data does make its way into an Access app that then becomes corrupt, there can be a cost associated with contracting an Access expert to fix your problem. Again, not a fault of Access directly, but something to consider.