Access not responding when opening table...

  • Thread starter Thread starter Norm Sash
  • Start date Start date
N

Norm Sash

Access 2007 / Vista 64 Professional

Problem: If I doubleclick a table in the database 90% of the time Access
locks up with "Access not responding". Occassionally it will open the table
OK. However, if I right click the table name and open it in design first,
and then switch to data display I don't seem to have any problem.

This behavior happens in multiple databases. I've created a very simple
database with just one table in it. Samething, doubleclicking the table locks
up Access 90% of the time. Right clicking the table, opening in design, and
then switching to data view doesn't seem to have a problem.

Same behavior on Querries. Any ideas? I've uninstalled Access 2007 and
then reinstalled it. No change.
 
I hope you have both Service Packs (SP1 and SP2) installed as well. If not,
try doing that.it usually helps. The problem occurs only rarely and seems to
be only on Access 2007 and Vista. In addition to the service packs, make
sure all your updates are installed.
 
Yes, I have Office 2007 SP2 and Vista SP2 installed, along with all updates.

Is this a known bug (seems implied in your response)? If so, any knowledge
of a hotfix or other work around?
 
I remember another post earlier this year with the same problem. I wasn't a
party to the post, so I'm not sure how or if it was solved. Does the same
thing happen when you open the Northwind sample database?

One other thing I can think of is that Access 2007 checks permissions at the
very beginning, so it might pay to build a Trusted Location and put the
database there. Just a guess however.
 
I just tried the Northwinds application with some interesting results. If I
open the NW database application and from there (with the application tabs
open) go to tables and doubleclick on different tables they seem to open
fine. However, if I close all of the NW application tabs and then just
doubleclick on a table Access locks up with the same problem behavior that
I'm having. I can open the table in design mode first and then go to data
view and it works fine, but if I go directly into data view it locks up.

One other note is that I noticed in the lower left corning of the Access
window it says "calculating...." when it locks up.
 
Forms that are based on queries often say "calculating ... " while they are
loading the recordsource. Since Northwind basically works, I'd try putting
your apps in a Trusted Location to make sure nothing interferes with the
code.
 
Thanks for your continuing replies, Arvin. Per your suggestion I set up a
trusted zone and there was no effect. The problem remains.

Also, I'm not trying to open forms in either my database or Northwinds
database.... I'm simply doubleclicking a table to open it in datasheet mode
and the system locks up, whereas if I open the table in design mode and then
switch to datasheet mode everything is fine.

And the Northwinds database is not working... it behaves the same as my
simple one-table database... it locks up when doubleclicking the table to
open it in datasheet view.

Any more ideas? What is so different opening in design mode then switching
to datasheet mode vs going directly to datasheet mode?

Thanks!
 
Thanks for your continuing replies, Arvin.  Per your suggestion I set up a
trusted zone and there was no effect.  The problem remains.

Also, I'mnottrying to open forms in either my database or Northwinds
database.... I'm simply doubleclicking a table to open it in datasheet mode
and the system locks up, whereas if I open the table in design mode and then
switch to datasheet mode everything is fine.

And the Northwinds database isnotworking... it behaves the same as my
simple one-table database... it locks up when doubleclicking the table to
open it in datasheet view.

Any more ideas?  What is so different opening in design mode then switching
to datasheet mode vs going directly to datasheet mode?

Thanks!
Click to expand...

Greetings All!

I am seeing the exact same issue - when I saw that this was today, I
figured I would chime in.
I had already tried the aforementioned steps before I ran across this
thread.
I am wondering what else we have in common here - Vista x64, Office
2007, current with service packs & updates, etc.
I can't think of anything else uncommon that may be obvious...
I am sure this is reproducible if anyone cares to test...

This sounds like "bug" to me.

Josh
 
The best way to debug a problem like this is to work backward.
Unfortunately, that isn't always possible because many updates can't be
backed out. The alternative is to start fresh and work forward. Try
uninstalling Office, rebooting, then reinstalling Office. Now try your
database. If it's OK, install the first Service Pack, etc. until the problem
rears its ugly head. If you can't back up from that point, start over, only
this time stop just short of the problem beginning.
 
In my case, this was a new notebook with Vista x64 Service pack 2
installed. The problem appeared after installing Office 2007, & it
remained after installing the latest updates. I also tried a repair
install (of Office) & uninstall & reinstall with no change. In other
words, the problem arises after installing Office 2007.
 
Access 2007 / Vista 64 Professional

Problem:  If I doubleclick a table in the database 90% of the time Access
locks up with "Access not responding".  Occassionally it will open the table
OK.  However, if I right click the table name and open it in design first,
and then switch to data display I don't seem to have any problem.

This behavior happens in multiple databases.  I've created a very simple
database with just one table in it. Samething, doubleclicking the table locks
up Access 90% of the time.  Right clicking the table, opening in design, and
then switching to data view doesn't seem to have a problem.

Same behavior on Querries.  Any ideas?  I've uninstalled Access 2007 and
then reinstalled it.  No change.
Click to expand...

I have exact same problem. I have only noticed it since upgrading to
Office SP2. (I also use Vista 64)

I have isolated the problem to just one table. The problem is
something to do with the data in that table. If I copy the table -
structure-only - then the copy can be opened but the original with
content cannot be opened.
It is not related to size ... I have bigger tables in same ACCDB.
All other tables in my ACCDB can be opened.

It IS related to database format. I can use same version of Access on
an identical copy of the table in a 2003-format MDB and the table can
be opened.
BUT, I then tried attaching that MDB to my ACCDB and I get same
failure.
I have tried Compact and Repair, importing the data.

There does appear to be some form of fault in Access.
 
Arvin... did you mean you were reporting the problem to MS? I'm assuming
that as my initials are NS and I don't think I have the answer to the problem
:)

Anyway, I continue to have the problem and have tried a number of things. I
even have a 2003 db that runs as an application just fine (exe). But if I
open it in Access 2007 and then just double click a table (doesn't seem to
matter what table), Access locks up. But again, if I first explicityly open
the table in design view first, then switch to data view, everything seems
fine.

Anyword from MS on this? One thing I haven't done is roll back Office or
Vista service packs.

-Norm
 
Hi Joshua... any changes in the problem for you? I'm still having it and
it's a pain. My configuration is:

Laptop with AMD x2
Vista 64 Ultimate with SP2
Office 2007 with SP2

I'm wondering if it has anything to do with running Office on Vista 64. Do
you happen to have a Vista 32 system that you could try this on?
 
I have the same problem, although I am running XP SP3. My database
was originally created in Access 2000, but converted to 2007. I have
been trying to figure out what causes it, but it is so sporatic, it's
tough to figure out what makes it hang. Has anyone tried linking the
table(s) to a blank database? I tried it briefly with one table and
it opened up just fine, which is even more perplexing.

I have even started a new database and imported all of the tables and
queries into a brand new database and have the same issues. I tried a
Repair and that did not work either.

Richard, since you have isolated it to one table, perhaps we can see
what our tables have in common to figure out what it is.

Do you have any of the following in that table?
Autonumber field
Memo Field
Any input masks stored in the table on any fields
Non-default field sizes
Custom Default values stored in the table

Also do you have a lot of relationships linked to that particular
table?

If so, let me know and perhaps deleting one field at a time might help
find out if it's a type of field that is causing the problems or maybe
it's a relationship issue.

Thanks.
 
I don't think we need to go to the level of comparing tables. I just simply
created a brand new database in Access 2007 with a single table in it with
only a couple of fields and no data.

I can get the failure to happen on that very clean db: open to data view by
double click the table name and Access locks up. Open to design view first
and then switch to data view works just fine.
 
Is anybody else running MapPoint 2009 on the same machine? Just a
long shot, but I belive that will install an Access Database Engine as
well. I am running it on my pc.
 
I don't think we need to go to the level of comparing tables.  I just simply
created a brand new database inAccess2007 with a singletablein it with
only a couple of fields and no data.

I can get the failure to happen on that very clean db:  open to data view by
double click thetablename andAccesslocks up.  Open to design view first
and then switch to data view works just fine.
Click to expand...

I'm also experiencing the same problem. My configuration is Vista
Ultimate x64 SP1, Office 2007 SP2. The machine is also a quad-
processor, though I'm not sure what (if anything) that would have to
do with affecting what's going on. So few run a single-processor
machine these days.

On this machine all tables in my access database open fine UNTIL the
table contains more rows than can be displayed on the screen without
vertically scrolling through the rows. That's when I get the same
lockup described in earlier postings on this thread.

I can reproduce this at will by taking a table with, say, 15 rows, and
opening it with the Access application window maximized. The fifteen
rows fit easily on my screen and everything's fine.

Then I restore the window (unmaximize) and shrink its size so only
about ten rows can show. Close the table and re-open it and voila -
Access hangs.

I have the same "workaround" as everyone else; if I open the table
first in design mode and then open it in datasheet mode it's okay.

But that doesn't help in trying to put together a split form or a sub-
form where I need the datasheet portion of the form to open in
datasheet view first, without first opening in design view as is
required in the "workaround".

Arvin, if you're still following this thread, where would the
appropriate place be for me to add this tidbit to your report?

Thanks,
-Chuck
 
I have exactly the same problem. Vista 64, Office 2007. All service packs and updates applied. My application works file. However, if I double click on the table to open it in a datasheet view, Access hangs. I exported the data to a text file. Created a new table. Imported the text file into a new database / new table....no change in behavior.

Has anyone found a solution yet.





Posted as a reply to:

Re: Access not responding when opening table...

I don't think we need to go to the level of comparing tables. I just simply
created a brand new database in Access 2007 with a single table in it with
only a couple of fields and no data.

I can get the failure to happen on that very clean db: open to data view by
double click the table name and Access locks up. Open to design view first
and then switch to data view works just fine.



:

EggHeadCafe - Software Developer Portal of Choice
WCF Workflow Services Using External Data Exchange
http://www.eggheadcafe.com/tutorial...a-6dafb17b6d74/wcf-workflow-services-usi.aspx
 
Whipmeister said:
Same problem. Office 2007 Ultimate/Vista x64/AMD Dual Core

Apps open fine in 2003 on an XP box. Clearly there is something awry in
the 64-bit OS/Access 2007 combination. I've been building commercial
quality Access and VB apps for 15 years. This one is not going to be
addressed with the catch-all "uninstall/re-install, make sure your
service packs are up to date, blah, blah, blah".

Been reported enough for MS to get someone busy chasing it.


--
Whipmeister
------------------------------------------------------------------------
Whipmeister's Profile:
http://www.thecodecage.com/forumz/member.php?userid=974
View this thread:
http://www.thecodecage.com/forumz/showthread.php?t=112252
Click to expand...
 
Back
Top