A subform is broken until I do something that shouldn't fix it

[cherold]

This is really, really weird. The tl;dr version is, I have a subform that won't work properly until I go into design view and open up a function from the s

[RuralGuy]

I would start by *importing* your db into a fresh new db and see if the problem follows.

[John_G]

I would get the error message, "Object or class does not support the set of events."

Are you compiling your code each time you make changes to it? If not, make it a habit to always do so. That will detect many errors you didn't know were there.

When you get that error, do you click "Debug" to see the line of code that is causing the problem? It's very difficult for us to help unless we have more information.

It's also weird that Access wants me to save the form even though I haven't made any changes.

But you did make a change - you set or removed a breakpoint in the code.

[cherold]

1) I haven't made any changes to the VBA code, the changes were only in the SQL for the subform.
2) The debug button does not appear on this particular error screen.
3) I find even if I don't set the breakpoint, just opening the VBA module from form design mode fixes the problem. If I go into design mode, open VBA, close VBA, and close design mode, then I have not made any change in the form. So why does Access ask if I want to save the form? What does it think is being changed?

Are you compiling your code each time you make changes to it? If not, make it a habit to always do so. That will detect many errors you didn't know were there.

When you get that error, do you click "Debug" to see the line of code that is causing the problem? It's very difficult for us to help unless we have more information.



But you did make a change - you set or removed a breakpoint in the code.