Runtime error 2467 when going into design view anyway

[Robyn_P]

Hello all, I'm stumped. I have a form with a hidden textbox and in the form unload event I check whether this is null. When I close the form using the x button or through the [Close] command button I've created all works fine, when I right click and go into design mode, the isNull statement errors with a run-tim 2467 object does not exist. I have no idea why. Any suggestions? I can add error catching code to ignore the warning but I would rather know why it is being triggered in the first place.

[June7]

I tried to replicate this issue and cannot. Post your code or provide db for analysis.

[Robyn_P]

I can't post the database, it's huge and the work system won't let me. The code that errors is [code]If Not IsNull(Me.txtHiddenID) Then[\code]

[June7]

I tried that and does not error. Is there more code?

Use forward slash in CODE tag.

[rpeare]

You will have to check for the state of the form

https://docs.microsoft.com/en-us/off...rm.currentview

you should only perform your code if the currentview is non zero (though I would limit it specifically to form view myself)

[Micron]

By any chance is there a subfom involved, or the form close button is disabled?

[Robyn_P]

The form close button is disabled and there is a subform. How could that be affecting it?

[isladogs]

Does your form contain a Web browser control.
I find changing to design view can cause an error in that situation.
If t helps, this is the error I have seen ...

[Micron]

The form close button is disabled and there is a subform. How could that be affecting it?

The day I asked that question I had found a forum where it was indicated that this can happen under those conditions (or so I seem to recall). It's been too long now so I can't remember why or what the fix might have been. Sorry.
Maybe you can find it if Colin's post doesn't help. I know that a subform opens before the main, so referring to a main field in subform load will cause issues. Don't recall if it also closes first. Maybe research that (or put a msgbox in both unload events so you can know which closed first) in case there's a connection between 2 forms that's causing it.