Slow opening Access database on network issue 1

[malibu65k]

Hi All,

I have an MS Access database, FE and BE. FE on users computer and BE on a Network drive. This works great on the Network in my building but when I place it on a Network in another building(different Network than mine) it runs very slow, even on opening the database, opening forms or saving any changes in the modules takes a long time. I can't imagine it being a database issue being that it works on the network in my building an not another.

Any ideas what I could do?

Thanks,
Kathy

 

[Ray1127]

First I'd check with the Network Administrator to see if there could be a router, gateway or bridge issue between the 2 networks.

 

[malibu65k]

It's not 2 Networks. Just client FE and BE on another Network

 

[MasterRacker]

SO you're saying that WorkstationA talking to ServerA on NetworkA works fine, but copying the files so you have WorkstationB talking to ServerB on NetworkB is slow?

I think you still need to talk to your Network Admins first. Are thhe workstatins comparable? Are the servers comparable? What about the speeds and configurations of the 2 networks?

Try simple file copies on each network and see if one is noticably slower.



Jeff
[small][purple]It's never too early to begin preparing for [/purple]International Talk Like a Pirate Day
"The software I buy sucks, The software I write sucks. It's time to give up and have a beer..." - Me[/small]

 

[malibu65k]

They are telling me that only MSAccess Databases run slow.

 

[Ray1127]

Ok so you have the front end on Workstations A and B. The Backend is on Server A. Workstation A and Server A are on Network A. Workstation B is on Network B. Workstation A to Server A works great. Workstation B to Server A is slow and is slow only for all MS Access Databases.

Still sounds like a network issue to me. There is something between Network A and Network B that is impacting MS Access. Not a network Engineer so I don't know what the possibilities are. Try copying the backend to a server on Network B and link the frontend on Workstation B to that backend and see if it is still slow when not crossing the 2 networkw. If it's not then it is definitely something between Network A and Network B. If it is still slow then there is an issue within Network B.

 

[MasterRacker]

Ray, the way I'm intrepreting her situation is that she has 2 BEs. Network A and Network B are not connected to each other at all. Kathy, is this correct?

Jeff
[small][purple]It's never too early to begin preparing for [/purple]International Talk Like a Pirate Day
"The software I buy sucks, The software I write sucks. It's time to give up and have a beer..." - Me[/small]

 

[jrbarnett]

Are you using mapped drives on network A and UNC paths on network B?
UNC paths for linked tables are always slower than mapped drives.

John

 

[Ray1127]

MasterRacker that's why I asked the question I wasn't sure I understood how it was setup and I thought it would be easier to answer her question if that was made clear.