Access XP Stalling

[Qube]

Hi

I am running Access XP in a multiuser env. I have the source held on the server and each client has an .mde with linked tables.

The problem is that the some of the machines hang / stall whilst using the database. It does not "stop responding", and the time that is displayed in the DB keeps updating. But I have to end the task and launch it again.

The machines are running Windows XP SP1a and Office XP.

This is has only started to happen since we moved from Windows 98 and Office 97.

I would be grateful for any help

Thanks

Lee

 

[JoyInOK]

You're problem may be a memory one. Windows XP uses almost twice as much memory as 98, and that's before you launch any programs. Our automation code would seize up just as you described. A memory upgrade did the trick.

 

[Qube]

Thanks for that.
I guess that is possible. However...
It does not lock up on all pcs (all pcs are brand new with same spec). The machines have 256MB ram each. I will however monitor this and see if this is the solution.

 

[Hap007]

Dear Qube,

I completely aggree with JoyInOk.

I do development on Win 98 PC (333megz) with 512 meg - runs fine.
I do development on Win 2000 Pro PC (1gig hrtz) with 512 meg - it runs fine.

I bought a Win XP Pro 2.4 gig hrtz PC with 256 meg ddr 2100 fast memory. Well it ran like an 'OutHouse'. Just trying to run Word or IE, and it almost halts. Then, I added another 256 meg of memory and all runs fine.

Point, Newer Operating system, double the memory to see same performance.

Note: I run Access 97, 2000, 2002 XP on all PCS

Hope This Helps,
Hap



Access Developer

http://www.fcs-software.com/fcsaccessdev.html

-
Specializing in Access based Add-on Solutions for the Developer

 

[Qube]

Thanks for that. I will try to add some more Ram and see if that helps.

 

[Qube]

Ok..
I have increased the Ram in the machines to 512 and I am still getting the same problem. Any other ideas ?

Lee

 

[Hap007]

Dear Qube,

Well, here is something to try.

1) Go to a PC that is giving you problems and just try to run Access. See if Access itself, with no mdb to open, will run ok.

2) Assuming 1 is ok, try to open a local Database, such as NorthWind and see if that runs ok.

3) Assuming 1 and 2 are ok, open your Code window of your first module or form that is loaded, place a code break point, then run/open db. See how long it takes to get there. If it works ok to that break point, then use 'F8' to step thru each line of code to see what is causing the delay.


Also,
Is your Anti Virus software examining the Access Mdb file when it is opening? (If your mdb is large, perhaps this is an issue.

Good Luck,
Hap


Access Developer

http://www.fcs-software.com/fcsaccessdev.html

-
Specializing in Access based Add-on Solutions for the Developer