Access frozen when opened

[vent]

Hi everyone

This morning when I went to open this project I'm working on, everything was frozen none of the tables, buttons, tabs or anything else worked. I tried opening and closing it a few times but each time it opened, everything was frozen. For the most part I use the 2007 - 2010 version, but yesterday I worked on this project using the 2016 version. I don't know if that has anything to do with anything but figured I should mention. I don't think I've done anything too out of the ordinary. This is the first time this has happened. Even the backup copy from yesterday was frozen, but luckily the copy from two days ago works fine. If anyone wants to share their thoughts, that'd be much appreciated.

 

[The_Doc_Man]

What do you mean by the "2016" version? More specifically, were you just using the 2016 version of Access on the database? Or had you also tried to do something to upgrade the project in some way? Your description appears to say that the problem started when you changed Access versions.

Your description makes me wonder just what you did. Do you know if your 2016 version of Access is the same "flavor" (32-bit or 64-bit) as the one used to develop the database? Because that can have some pretty ugly effects.

Can you even get into the database navigation screens or had you blocked that off?

 

[vent]

Hi

I meant the latest version of Access, which is Access 2016. And yes I was using this version on the database because normally I use the 2010 version however yesterday I was relocated to a different computer which had the newest Access installed. I didn't "upgrade" anything though, I just fiddling around with trying to get a form to filter a report. So adding something new to the existing database. I believe both were 32-bit version as indicated in the About/Help section of each version. When I open the database on the machine I regularly use (not the 2016 version) absolutely everything was blocked off, not even the max/min and close buttons worked, literally everything. I had to close it by right-clicking the access icon and hitting 'close'.

 

[static]

Hold the shift key down while you open the file.

If it works normally, a macro or some VBA that runs on load is having a spaz.

 

[isladogs]

Its probably a reference issue caused by swopping back to an earlier version of Access

To check this, go To Tools then click on Visual Basic Editor.
When in the VBE, go to Tools..References.

If any are marked MISSING (probably with 16.0 in the reference name) you need to replace with the Access 2010 equivalent

After that, compile the database & it should then be OK

NOTE:
1. If you need more guidance see my post in the Code Repository:
https://www.access-programmers.co.uk/forums/showthread.php?t=293716

2. If you can't open your database to get to the VBE, try holding the Shift key down as you open it. This will disable any startup conditions you are using

EDIT - just noticed that static mentioned point 2 whilst I was typing this

 

[vent]

If any are marked MISSING (probably with 16.0 in the reference name) you need to replace with the Access 2010 equivalent

by marked MISSING do you mean the available references that are unchecked? Because I'm looking at this now the first four are marked checked but everything else downward is unchecked

 

[isladogs]

No - I meant whether any of the checked references have the word MISSING next to the reference name.

Your answer suggests all 4 refs are fine

OK do the following:
Make a backup of your database - ESSENTIAL

Then do each of the these in turn
Close & reopen the database after each step

1. Compile - if it fails, fix each error it picks up in turn
When all is OK go to 2.

2. Compact & repair

3. Decompile again - this removes any corrupt compile code
If you don't know how to do this, see this thread & read the link it gives

https://www.access-programmers.co.uk/forums/showthread.php?t=176511

4. Compile again

5. Compact & repair

If after all that you still have problems, then create a new empty database.
Make sure the references are identical to those in the existing db

Then COPY all items from your existing database including any hidden objects but excluding system objects

It may take a while but you should get a working db again after all that

 

[vent]

If after all that you still have problems, then create a new empty database.
Make sure the references are identical to those in the existing db

Then COPY all items from your existing database including any hidden objects but excluding system objects

By this do you mean, essentially importing everything into this empty database? I've heard doing this would be beneficial just never did it before

 

[isladogs]

Yes - but you only need to do it if all the other steps fail

If you create a new db, remember to compile then compact at the end.

Oh yes & don't forget to BACKUP first
Yes I know I said that before ....

 

[CJ_London]

just a check - is the database split and each user has their own copy of the front end? if not and more than one user can access the db (particularly if they have different versions of access) then you may have corrupted it.