A colleague and I have spent a lot of time on this to no avail, so any hints as to what the problem may be are very welcome.
I have developed a fairly complex Access db (not split) that runs perfectly on four completely different machines (some new and fast, some old and slow) using variations of Windows XP.
I have run it in Access 2003, 2007 (both with and without SP2) and 2010, all fine.
On three other machines (all the same: HP 3010SFF, dual core E5400 2.6GHz 3Gig RAM XP pro), using Access 2007, the db “hangs”.
We discovered the hanging was due solely to one table not opening (i.e. all the other tables open perfectly). Thus we stripped out everything except the dodgy table.
We tried all the following on two of the “hanging” machines, but nothing stopped the hanging:
Re-installed Office 2007;
Tried with and without SP2;
Reduced dodgy table by deleting fields and records step by step, to two fields and zero records;
Created new table in a new db by importing data from dodgy table in hanging db, as CSV. The new table in the new db hung;
Cut and pasted data into a new table in a new db. It hung;
Changed the name of the table;
Changed names of field headings;
Stopped all anti-virus software and switched off firewalls;
Changed folder option in Windows to stop automatically looking for network drives;
Changed all fonts to Arial;
Disabled all non-Windows start-up items in msconfig;
Ran “detect and repair”.
On a working machine, I have set the dodgy table up with about 200,000 records (it has 41 fields) and it opens almost instantly.
When the db hangs, the processor runs at 0% for Access. This suggests these computers are waiting for something (hence the ideas for msconfig, AV software etc etc.). Obviously, I don’t have a clue what’s going on!
Thanks for looking.
Skeletal
I have developed a fairly complex Access db (not split) that runs perfectly on four completely different machines (some new and fast, some old and slow) using variations of Windows XP.
I have run it in Access 2003, 2007 (both with and without SP2) and 2010, all fine.
On three other machines (all the same: HP 3010SFF, dual core E5400 2.6GHz 3Gig RAM XP pro), using Access 2007, the db “hangs”.
We discovered the hanging was due solely to one table not opening (i.e. all the other tables open perfectly). Thus we stripped out everything except the dodgy table.
We tried all the following on two of the “hanging” machines, but nothing stopped the hanging:
Re-installed Office 2007;
Tried with and without SP2;
Reduced dodgy table by deleting fields and records step by step, to two fields and zero records;
Created new table in a new db by importing data from dodgy table in hanging db, as CSV. The new table in the new db hung;
Cut and pasted data into a new table in a new db. It hung;
Changed the name of the table;
Changed names of field headings;
Stopped all anti-virus software and switched off firewalls;
Changed folder option in Windows to stop automatically looking for network drives;
Changed all fonts to Arial;
Disabled all non-Windows start-up items in msconfig;
Ran “detect and repair”.
On a working machine, I have set the dodgy table up with about 200,000 records (it has 41 fields) and it opens almost instantly.
When the db hangs, the processor runs at 0% for Access. This suggests these computers are waiting for something (hence the ideas for msconfig, AV software etc etc.). Obviously, I don’t have a clue what’s going on!
Thanks for looking.
Skeletal