Any downside to executing an Application Object from one Access database to another?
Posted on 2013-09-17
I have a split Access 2007 database. The front end is distributed to about 20 users who run it on their desktops. The backend which houses the data is out on a server and the users link to the tables. When remote users use the databse it is extremely slow because Access does all of the queries at the users desktop and so it transferring a large amount of data.
To get around this I have been doing some tests using the Access Application Object process, sending the request to the backend database and running the queries there. Then the data is appended to a temporary table and then it is pulled to the front end database. This speeds up the process exponentialy as only small amounts of data are passed back and forth.
My question is are there any downsides to doing this? Usually there are only 5 or 6 users on the databae at a time, but on Fridays it can be up to 12 to 15.