Share via

Access hanging / not responding

Anonymous
2016-08-25T15:46:20+00:00

I have an Access 2010 database which worked fine until recently. Now, it constantly 'hangs' for upto 15 minutes at a time, regardless of the action I am doing. for example, when I right-click to open a Query in design view, it hangs.

When I just click the mouse into a field, it hangs before it will allow me to enter any text. It is taking forever to build this database and create/test queries.  All the queries are those Ive created, there is no VBA

Ive tried Compact and Repair, and also re-buildt the DB from scratch with no luck.

The database sits on a shared drive at work, and have various links to other Access tables and Excel worksheets, also on the shared drive. I am the only user of the database itself. The outputs are to pivot tables which others use.

Can anyone advise why it hangs like this with every keystroke that I make?

Thanks in anticipation :-)

Microsoft 365 and Office | Access | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

3 answers

Sort by: Most helpful
  1. Anonymous
    2016-08-29T18:04:28+00:00

    same thing here....just wanted to open a local database, everything I do makes Access not respond for 1-2 minutes, windows 10, updated, access 2010, cpu, ram, hdd & net all free. I just hate it when I have to do something quick and microsoft gets in the way...

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2016-08-25T16:25:54+00:00

    Thanks for your response.  I understand your comments and where youre coming from. I guess I did this in the live environment as Im the only user of Access here.  Its not too large a database, and until a couple of days ago, everything worked fine.

    I will try out your suggestion though, thanks

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Tom van Stiphout 40,211 Reputation points MVP Volunteer Moderator
    2016-08-25T16:19:16+00:00

    For one thing you're operating in a non-standard environment. It is bad practice for a developer to make changes to a Production system while it is being used. Perhaps it is time to get a real development discipline. That's too big of a topic to discuss here in detail, but elements include:

    Dev / Beta / Production are different stages of the development life cycle, and the application moves through these stages in a deliberate fashion.

    Management decides what developer shall implement for the next version.

    Developer implements this on his/her local machine, using local resources (e.g. copies of the Access databases and Excel worksheets)

    Developer unit tests, increments version, and offers it to the Beta test team.

    Beta testers exercise the new functionality (and some of the possibly affected existing functionality) using local resources, report bugs, and test some more until satisfied.

    Developer deploys to Production.

    Was this answer helpful?

    0 comments No comments