Access running slow on specific PC

[dsatino]

I'm hoping someone has some direction on this. Yesterday, for no apparent reason, any access program that I run off of the network is extraordinarily slow. From loading forms and reports to running queries. Things that used to take milliseconds now take 20 minutes.

Any Access program that I run from my C:/ drive is fine which made me think that network was just overloaded, but it's not. I can run the same network Access programs from my other PC just fine with no performance issues.

Long story short, something has changed on my primary PC and I have no idea what it is. Access seems to be the only problem affected.

As further background, I had been playing with priorities on the Task Manager, but I thought they all reset once Windows restarted. I also killed a process that was eating up memory for no apparent reason.

I'll pretty much try anything, so feel free to throw anything out there.

Thanks

[beacon]

Hi dsatino,

If you have a backup of the database, you may want to reinstall Access on your primary PC. I'm not basing this on any facts, but I suppose it's possible that the process you killed negatively affected something in Access, which is causing it to not process as it should.

[pod]

Try compacting and repairing your database also,
this might not resolve you problem, but it won't hurt

P;oD

[dsatino]

Update: My PC crashed due to a hardware problem (Heat sink) of all things.

I had my harddrive wiped clean and totally reimaged.

No change! All my Access programs on the network are super slow.


(pod, you work in the Grand Rapids State Office Building?)

[MMcCarthy]

It sounds then like the problem is with your network connection. Although you may not be seeing this with other applications it would show first with Access. Access is a memory hog and has a lot of problems with slow network connections.

[dsatino]

Yes, but I have another PC sitting right next to it. I have no problems with that PC...

[MMcCarthy]

I assume they use different network sockets though. Get someone to check the connection on the socket used by the problem PC.

[dsatino]

Thanks, will do.

[dsatino]

Thanks Mary, it was in fact a problem with the subnet. Once I moved it over to run on the other subnet, everything is back to normal.