Form Locking up & all formula fields returning #name?

[halabis]

Last week I updated one of my forms with 156 new fields. Friday night when I closed the database everything was working fine.



When I came in this morning the form refused to load. Access would lock up and i would get a message that it was not responding. Eventually I was able to get it to load by opening the form in design view, then going into layout view, and then finally into form view. However none of my calculated field are functioning, with every single one returning a #name? error. Neither is any of my conditional formatting. I have double checked everything, and all the references are correct, and my conditional formatting is still there. It just isnt calculating.

Also, none of the broken fields are the new ones. They are fields that have been in this form for years, and I didn't make any changes to them with the recent additions to the form. All of the new fields are working perfectly fine.

What could possibly be causing this, and how do i fix it?

[RuralGuy]

Start by making sure you have a backup! Hopefully you can reliably open the db with the <SHIFT> key down. Assuming that, open one of the modules or a code page of a form and then check for BOGUS MISSING references by going to Tools>References. If any are listed as MISSING, make a note of it and uncheck the box. Close the db and then open it again and see if the issue still exists. Post back with results.

[halabis]

Some times when I open the form I am getting false fields that dont actually exist on the sheet at all. I have no idea what is going on.

[RuralGuy]

Try *importing* everything into a fresh new db and see if the issue follows. It only takes seconds.
https://btabdevelopment.com/how-to-i...-new-mdb-file/

[halabis]

That worked! Thanks! Any idea what was causing the issue, or why that fixed it?

[RuralGuy]

Hard to say. Glad you got it sorted. My signature has link to show how to mark thread as Solved.

[Missinglinq]

Any idea what was causing the issue, or why that fixed it?

If that fixed the issue, it's a good guess that it was corruption, and in most cases, as Allan said, it's hard to tell what causes the corruption. If we knew the cause(s) we could always avoid them!

Linq ;0)>