Access Split Database runs slow

I create split databases across the United States and I run into the split database in Atlanta Georgia running slow. In Atlanta they use a laptop vice a PC. What can I do at my end or do at their end to speed the database up.
lhtilaAsked:
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.

Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
Standard Access apps simply don't perform well across a WAN network, unless that network is VERY fast and VERY wide. Given that you're (apparently) spanning quite a bit of mileage (across the United States), I'd be willing to bet you don't have a fast and wide WAN. Only fix for that is (a) move to a different environment/approach or (b) use an alternate method to run your Access db.

For the (a) portion, you could move your backend to a server-type backend (like SQL Server) and modify the application to take full advantage of that platform. This would include using only filtered datasets (i.e creating forms that return only a handful of records based on user-entered criteria), moving all processes to the server where possible, etc etc. This can take a LOT of work, and the overall result may still be less than desirable.

For the (b) portion, you could use a RDS or Citrix setup. Users would log into the RDS/Citrix environment and run the app from there, and the only thing passed back across the connection are KVM (Keyboard, Video and Mouse). Everything else runs on the server, and processing is generally much faster. This takes money to setup, since you must have the OS and licensing to handle it, and you would need to insure your copy of Office is RDS-compliant.

Whether your users run a laptop or PC makes little difference UNLESS those laptops are connecting over a wireless connection. If that's the case, then you'll have nothing but trouble with that, and you should train your users to plug their laptops into a wired connection if they must work with your application.

Of course there's always the "fix" of rewriting the app in a more compliant technology, like a web-based front end. Those typically handle distributed users much, much better than any desktop-based program - but of course you would have a ground-up rewrite.

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
crystal (strive4peace) - Microsoft MVP, AccessRemote Training and ProgrammingCommented:
expanding on Scott's excellent advice, if your laptop user plugs in and is still slow, increasing the RAM (Random Access Memory) will speed things up too
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
This takes money to setup, since you must have the OS and licensing to handle it, and you would need to insure your copy of Office is RDS-compliant.
I forgot to include in that list the necessary hardware to run the RDS or Citrix environment, plus the technical know-how to setup and maintain it. Those can add quite a few dollars to the bottom line cost as well.
Your Guide to Achieving IT Business Success

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
I'd just add to Scott's comment that while a Citrix/RDS environment is not exactly cheap, it usually is the cheapest solution for remote office/workers.

 A re-write either with a SQL Server back end or as a web application can be far more expensive in time and money.   A Citrix/RDS setup is basically "plug and play" for your app just the way it stands.   You just need a box, the OS, and the licenses.

There is one other option out there as well:

www.eqldata.com

 This is not quite the same thing as a Citrix/RDS environment, but functionally it's the same.  Your remote users are not executing MSACCESS.EXE directly, but interact with a server that does so on their behalf.

Jim.
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
it usually is the cheapest solution for remote office/workers.
I agree, and (to me, anyway) this is the best way forward, for the least amount of hassle.
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
BTW, sorry if I repeated anything...busy day and I didn't read through all the comments in detail.

Jim.
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.