Inconsistent Run-time error 2467 referencing control that definately exists

[Robyn_P]

Hi guys,

I have a weird one for you. I have a form which has a hidden textbox called txtHiddenID. In the unload event of this form I have code that checks to see if this textbox is null

 if not isnull(Me.txtHiddenID) then  
    ' bla do stuff
End If

When I put the form into design mode the first time after it has been opened, the if line of code throws a 2467 error (object is closed or doesn't exist). If I hit "End" on the error message to exit the code and then try and change the form to design mode again, it works fine. No error. It's not a huge problem as it never seems to throw the error when you close the form through the close button so if you're as stumped as me that's fine, but I'd be really interested to know if anyone has any ideas what could be going on.

[ranman256]

what event is this code in?

[Robyn_P]

It's in the unload event.

It's an unbound form for data entry which has a subform and this field is used to link the subform records. Not sure if that's relevant.

[dashiellx]

It's in the unload event.

It's an unbound form for data entry which has a subform and this field is used to link the subform records. Not sure if that's relevant.

Are there any records on the subform? If there are no records in the subform, then the subform object does not exist-that might have something to do with it.

[Micron]

It's in the unload event.

It's an unbound form for data entry which has a subform and this field is used to link the subform records. Not sure if that's relevant.

Likely is, but without seeing your db impossible to say for sure. You might have a calculated control, or linked controls/fields (between main and subform) that has a reference that cannot be resolved because of the order of events. For example, a subform loads before a main form, so if you try to reference a main form during subform load, the main form isn't open so you can expect an error. Your solution might be to place your code elsewhere.