“The PCA crew is leagues above
the competition” - Pepsico
"a prior vendor failed to develop
the application, which (Practical) delivered." - Franklin Park
"the application (is) easier to use, with a
much simpler, more intuitive use interface" - Royal Administration Services
"Sometimes it's the things you don't ask for
that are important" - Royal Administration Services
"PCA turned our raw data and algorithms into easy to use
and understand features and reports." - CareScout
"The quality and professionalism ... has been
so outstanding that we want to send you a letter of thanks." - USALCO
"PCA people and applications stand out by
far exceeding our expectations." - USALCO
"The resulting application greatly increas(ed)...
our business effectiveness and efficiency." - The Advest Group
"PCA completes projects
efficiently and effectively" - Pepsico
MS Access Datastore
The MS Access data store application design uses a single back-end MS Access datastore that is connected that is connected to a Windows application Client, which is typically written in Java or VB or one of the Dot Net languages (e.g. C# .NET or VB.NET).
The MS Access Datastore approach uses MS Access exclusively as a datastore, and is generally useful for “occasionally connected” applications that need to be deployed to a standalone PC like a laptop or notebook. MS Access Datastore applications are best suited to referencing information (primarily “read” more than “write”), and frequently the MS Access synchronization capability to used to periodically update and share data.
MS Access Datastore Scorecard
| # End Users | < 15 | Assuming primarily Read-only usage |
| Deployment | Desktop Only | LAN or WAN not recommended |
| Performance | Varies | # of users, records, and datastore size dependent |
| Reliability | OK | Reliability can degrade beyond Read-only use |
| Data Integrity | Poor | Limited means to insure data quality and completeness |
| Security | Poor | Security is as good as the PC is secure |
| Data Limit | 1GB | More data will impede performance and reliability |
| Maintenance | High | Manual only; requires End Users to maintain |
| # of Records | < 50,000 | More records will impede performance and reliability |
| Internet Access | No | Remote access will substantially impede performance and reliability |
MS Access Datastore Limitations
The MS Access Data Store method can be used to house data on a network file share, however the Data Store approach forces MS Access to handle multi-user data concurrency issues, which are always best handled by a database server, and therefor can and will impact performance.
Limitations to the MS Data Store Application approach generally include data integrity and security issues inherent with all MS Access file-based solutions. As a desktop product, this model does not lend itself to centralized maintenance — MS Access Repair and Compact must be run by the end users. In the end, this design is as costly to develop and deploy as a full Client-Server application, but lacks the full Client-Server benefits of centralized Security, better performance, and ease of maintenance.
Read about Converting MS Access to SQL Server to solve these issues or contact Practical Computer Applications (PCA) directly at 877-843-3405.
Most Popular Pages
Recent Posts: Practical Blog
- Power View empowered practical Smart Client applications
- Tableau vs Qlikview and Tableau vs Spotfire
- Data, Story, View: Prototype and Update
- 2012 starts with Tableau 7.0
- SQL Server 2012 is good for Data Visualization
- Spotfire 4.0 is available
- Introduction of QlikView 11
- VisiCalc jubilee and history of Excel
- Data Visualization 2011: Omniscope 2.6
- Data Visualization 2011: Spotfire 3.3, Silver 2.0
- Data Visualization 2011: Tableau 6.1
- SQL Server 2012 is released for Preview



