Solved: Access 2007 - Split DB Across Company Network

Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

Steve060431

Thread Starter
Joined
Dec 18, 2012
Messages
7
Well, I've split my Access DB and it turns out that I am a little disappointed in the speed between the Front End and the Back End over my company's network. I was under the impression that a DB set up this way would be more efficient to use.
The Back End is in a shared folder in Philadelphia, I am in Chicago, and the location farthest from the server is in Seattle. How do I improve the response time of the DB across our network?

I know the closer the back end is to my physical location the faster I am able to run reports and navigate through the DB. I've been testing this all evening and night, but even in the middle of the night the application portion is still very sluggish and that's with no one on the network.
Back End:
On my desktop = Extremely Fast
On our Local Server = Moderatley Fast
Farther than the Local Server = Very Slow

If anyone has any suggestions I would greatly appreciate it.
 
Joined
Jun 8, 2001
Messages
2,583
Steve,
There's a lot more to speeding up an access database than splitting into FE and BE. One important thing if this is a WAN then Access is not a good answer. WANS are 100 times slower than LAN.

There are lots of ways to make access better accross a network.
1. move static tables to the FE.
2. make sure all forms are query based (not table). Bring only necessary data to the Forms.
3. Index important data. DO NOT over index.

If you google "slow access database over network" there are tons of tips on how to make it better.

One solution may be that you place a BE at each site and develop a process to perodically consolidate the data. I also recommend that you 'Version' the FEs. As you develop\enhance\repair and more people start using the thing its hard to track who is using the latest and greatest release. I would also incorporate a way to 'lock users' out of the database so you can perform maintence.

Any platform accross a network is major undertaking. We have 100 users on one BE. Its on a local server and to maintain we often remote to a local workstation in order to get reasonable response time.
 

Steve060431

Thread Starter
Joined
Dec 18, 2012
Messages
7
Thanks Dan,
I appreciate the info -- I think I will go with the consolidated route. I'd like users to be able to get in and out quickly, and with our network I don't think that will be a possibility. Again, thank you and have a great weekend.
 
Joined
Jun 8, 2001
Messages
2,583
Good Luck Steve, those darn users alway complaining about 'speed' but once you get it humming not one Thank you!

Let me know if you have other questions. Seriously, Version the FE and add the user 'lock out'. It will be big deal if you get a lot of people on this thing.
 
Joined
Apr 21, 2012
Messages
8
Hi Steve,

A slightly different approach is run the Front End application in a Windows Terminal Server or Citrix XenApp server located in Philadelphia, and then have the users access this using MS Terminal Service Client or a Citrix Receiver (client). That way all file access is local.

Best regards...Paul
 
Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

Users Who Are Viewing This Thread (Users: 0, Guests: 1)

As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 807,865 other people just like you!

Latest posts

Top