Hello all. Just joined the forum. David M. from Chicago. Hope everyone that reads this is in the best of health and spirit.
I am not sure if this is the right place to post this question but...
Is it possible to link the back-end of one split database to the back-end of another split database?
The issue I'm having is slow performance from the database when working remotely or at home as opposed to in-office.
I am working with Access 2010 version and the .mdb split db files are located on a company network drive. The database back-end has one main table. It has approximately 185 fields and about 2700 records total. The front end is linked to the back-end and has 15 forms. Each form has at least 20 to 35 bound control fields.....with a good number of them being calculated control fields. Not to mention all of the unbound control fields. Each form has it's own query as a data source and they all have macros and vba coding running in the background. The front end file size itself is no bigger than 13 megs. I am not sure how many controls each form specifically has but I know its significant and suspect its the reason why the db takes so long to load.
In office, the database works okay....meaning, it's not slow. But working remotely, it is a nightmare. It takes between 2 to 3 minutes to fire up. Once in, opening a form takes anywhere between 30 seconds to 2 minutes.
What I have tried already is creating another smaller regular db (non-split), with just one query, one small form with perhaps 5 fields at most.....and I have it linked up to the main back-end db table of the current db. I tested it out while working remotely from home and although it is just one small form with a smaller query as it's data source, it still takes long to load. I am only guessing that aside of the fact that I am working remotely, load time is slow also because I am still indirectly linked to that larger, slower front-end via the back-end of the main split db.
The person I report to suggested creating another smaller database, split it so that it has its own front and back end.....then link the smaller back end to the first back end. So again, my question is....
Is it possible to even do that? (I haven't tried yet)
If so, will something like that even work?
My team has approximately 7 users and they all work off of an .mde copy of the db front-end. 5 of the users work remotely and they have grown grey hair waiting on this database to load and there is no end to their frustration and complaints.
Any and all suggestions are welcome and appreciated.