Why Access? Because it was simple to implement. Access required no IT support to setup or maintain. Access is blazing fast when installed on a network drive (LAN) or local drive.
During my search for a CAD library solution I found widely varied opinions about using Access databases. Here are a couple of articles that influenced my decision.
Microsoft Access Database Scalability: How many users can it support?
Using a WAN with MS-Access? How fast, how far?
Mistakenly Blaming Microsoft Access instead of the Developer
Most hardware design teams are small, typically 10 members or less, so Access's limit of 255 connections is not an issue. A well designed Access database (CAD Library) can easily support 20 to 50 users.
Most importantly the database must be split with a backend to hold the data and a user friendly front-end (GUI) to edit and add records to the backend.
Access databases are not true databases like SQL severs, however a well designed Access solution does support multiple users simultaneously.
During the past 4 years I have seen a growing interest in using Access as a database library.
Parts website traffic (past 4 years)
Parts is a turnkey Access database for Altium DbLib and SVNDBLib.
Numerous visitors have downloaded and used the FREE Parts database as a starting point to create their own database library.
Users can create their own front-end application, purchase Parts Front-end keys or use Altium's DBLib interface to add or edit records.
I recommend testing any solution, be it Access or SQL Server before making a decision.
Due to it's simplicity Access has proven to be a great solution for database libraries.
Download Parts and see for yourself how Parts can dramatically increase your productivity.
To request a demo use the Contact Parts page.
Happy New Year to All !
