For Ms Access 2016 the size is 2GB, if we have 100 tables in BE how do we create 20GB space? Its just a suggestion what if we do the following:
(1) Put all related tables with referential integrity in one backed for example a sales accounting will have the following tables :
- Price details
- Invoice line datails
- Receipts/Line details
- Credit notes/Memos
As long as the RI remain intact in blocks of 10 (Total BEs required 10)why can't an application work well, even I have not tried it , I still think that is the other way to get around 2GB limit
My current BE has 110 tables but is seating at 2.56MB while my FE is at 11.15MB which quite okay, I'm simply looking at the future, I have seen the challenges on migration , its very involving see below:
Configure SQL Server
Use the data diagram that is part of your development plan to implement the first
version of SQL Server objects, such as tables, views, and stored procedures.
Implement users, groups, and roles as needed. It is important to have these
objects in place before development starts—developers can’t work against a SQL
Server backend that isn’t there. Don’t worry about performance optimization yet,
that happens later.
Based on your development plan, staff your development team and provide the
resources necessary. Make the existing Access application available to the team
for use a benchmark or prototype resource. Keep an eye on the milestones and
risk areas defined in your planning process.
Before the first test deployment of the new application, basic developer-based
testing should occur. Use the existing Access application as a model to reduce
the amount of time needed for the initial testing effort. Compare each functional
area in the original Access application against the new code base. If you are
completely rewriting the Access front end application as well as moving the data,
you should plan to involve dedicated quality assurance/testing staff to find critical
Most Access applications are created by end users, and as such, lack
documentation. Since you are investing in the process of upsizing, now is a good
time to spend some time documenting the new application. At a minimum, create
a configuration and troubleshooting document that outlines where the
application’s component parts reside, desktop and network settings, and basic
troubleshooting techniques based on the results of your testing plan. If you have
the resources, you may want to consider more complete documentation in the
form of data diagrams, flowcharts, code listings, etc.