Microsoft Access, Relationship databases for even the smallest players.
April 08, 2021
Microsoft Access, Relationship databases for even the smallest players.
Score 7 out of 10
Vetted Review
Verified User
Overall Satisfaction with Microsoft Access
Many different use cases can be applied to Microsoft Access. More recently we have been using this to perform automatic joins when the input files will not change. This will eliminate the need for end users to utilize vlookups as they would normally. Since these types of joins can happen at any level of the organization, we are using access for the more localized locations where network connectivity isn't available and they can rely on a local database structure.
- Combining files
- Search large datasets quickly
- Roll out to single or multiple locations with limited ease and implementation cost
- Scalability between different versions
- 2GB Size limit before SQL migration needed
- Lack of availability to access via the web without SharePoint
- Corruption of files can happen, leading to VB being erased. Frequent backups are needed
- Local Relationship Database capability.
- Easy rollout as needed.
- Can show significant time savings to the end users for even the smallest of tasks.
- ROI for Microsoft Access is quite high. Usually included with Professional licenses, any savings are immediately realized.
- Ability to see the time wasted when a database can run automatically just by opening the file.
- As the systems that feed the Databases change, these stand-alone databases are usually the last thought of aspect but can have a large impact on a local users day.
Do you think Microsoft Access delivers good value for the price?
Yes
Are you happy with Microsoft Access's feature set?
Yes
Did Microsoft Access live up to sales and marketing promises?
Yes
Did implementation of Microsoft Access go as expected?
Yes
Would you buy Microsoft Access again?
Yes