I appreciated this problem sounds impossible! Between us, my colleague and I have built many dbs and have never seen anything like this before. I’m not at the computers for a while so can’t quickly try it. If I did it when running for real, I think it would just show code that had stopped, waiting for the dodgy table/associated query to open/run. I admit I’ve not tried control-break, but I’m not sure what it would show because, as I say, there is no code running in the test db. When running the db for real, any operation that involves the dodgy table will also hang (e.g. The hour glass is showing and task manager shows 99% idle. The table frame is there, and an area corresponding to the top right cell/heading is selected, but no records ever appear. The dodgy table stops opening after step 1. Over the next few seconds, depending on size, all the other records will start populating the frame and you will see the right hand scroll bar shrink as more records appear. The first few records appear and fill up the outer framework ģ. The outer framework appears and the top left cell and its field heading are highlighted Ģ. The table will “open” on the right hand side “work area”.īut this “opening” is actually in three visible stages:ġ. In Access 2007 or 2010 open up the “Task pane” on the left hand side where you can select the various Access objects. Forget code, queries, forms etc etc, it is just one table. We can reproduce the fault in a new db that ONLY consists of the dodgy table (or data imported from the dodgy table). As it is standalone, clearly, this cannot be an explanation.īecause another easy explanation of hanging is dodgy code, our tests involved tracking down which area was causing the problem, thinking it would be code. The only reason I talked about splitting is that one cause of “hangs” is the network connection between the front and back-ends. There is only one user and the db is standalone there is no shared data. Sorry for the delay in replying, I was out yesterday. Obviously, I don’t have a clue what’s going on! This suggests these computers are waiting for something (hence the ideas for msconfig, AV software etc etc.). When the db hangs, the processor runs at 0% for Access. 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. Stopped all anti-virus software and switched off firewalls Ĭhanged folder option in Windows to stop automatically looking for network drives ĭisabled all non-Windows start-up items in msconfig The new table in the new db hung Ĭut and pasted data into a new table in a new db. Reduced dodgy table by deleting fields and records step by step, to two fields and zero records Ĭreated new table in a new db by importing data from dodgy table in hanging db, as CSV. We tried all the following on two of the “hanging” machines, but nothing stopped the hanging: ![]() Thus we stripped out everything except the dodgy table. ![]() We discovered the hanging was due solely to one table not opening (i.e. On three other machines (all the same: HP 3010SFF, dual core E5400 2.6GHz 3Gig RAM XP pro), using Access 2007, the db “hangs”. I have run it in Access 2003, 2007 (both with and without SP2) and 2010, all fine. 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. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |