Any downside to executing an Application Object from one Access database to another?

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.
Scott PalmerData AnalystAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jeffrey CoachmanMIS LiasonCommented:
Just make sure to add in; error handling/Validation/Rollbacks, ..etc,  so that if any part of this system fails, you revert back to the original state.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Scott PalmerData AnalystAuthor Commented:
Thanks, had not thought very hard about those things.

Jeffrey CoachmanMIS LiasonCommented:
...for example, if the computer crashes in the middle of creating the temp table, ...etc
...Glad I could help...

DatabaseMX (Joe Anderson - Microsoft Access MVP)Database Architect / Systems AnalystCommented:
"Then the data is  appended to a temporary table and then it is pulled to the front end database. "
I don't quite get it. If the tables in the FE are linked to BE ... and you are running queries in the BE directly on those tables, why do you need a Temp table - and what is there to pull back into the FE ?
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.