Monica Main form, opens with database, straight forward. I double click on "DB" under Delica Type and I get this:

The "BeadTypeID" is hidden but pulls from which ever type was selected on the main form. The five tabs on the left are original. Last one on the right is the new/problem child.

Notice, "BeadTypeID" is on the form. It is in the query that feeds it, and I've double checked that it is the same as the original Project tab, pulls the ID in the same way, even copied/pasted the name over to the new form's query to verify no spelling differences. The subform itself performs just fine, I slide it out of the way no error messages. If I close the window from this form, I get the below error message. If I click to a different subform before closing, no error message. If I go to the new form and slide the window around, no error message underneath. Only when I close from the new subform. I'm out of ideas of where I should be looking.

Got any code in those forms?

Check your queries for misspelled field names?

Hi Monica Search for Forms!DelicaBeadF!BeadTypeID.value and show us where the code is.  John

My code for that form is below. I searched the whole project and the only time that's referenced is on one of the other tabs (that doesn't give that error).

This could be because Access is trying to resolve that reference to Forms!DelicaBeadF!BeadTypeID right as the form is closing, and at that point the form is already unloading, so the reference no longer exists. That's why everything works fine while you're using the form, but you only see the error when you close it while that tab is active. When you switch to another tab first, that subform isn't being evaluated anymore, so no error.

This almost always comes from something in that subform still pointing directly to Forms!DelicaBeadF!BeadTypeID, either in the RecordSource, a control's ControlSource, RowSource, or a filter. Even if it looks identical to your other tabs, one small difference is enough to trigger it.

The best fix is to stop reaching up into the parent form like that and pass the value properly. If you can, use Link Master Fields and Link Child Fields with BeadTypeID so Access handles it automatically. Otherwise, inside the subform switch that reference to Me.Parent!BeadTypeID instead of using Forms!DelicaBeadF. That keeps everything within the form hierarchy and avoids this exact issue during close.

Bottom line: nothing is actually broken with your data or logic. It's just Access trying to evaluate a form reference that no longer exists at the moment the form is closing.

Found it!!!!!!! I finally got to a point where I made a copy and just started deleting things until I didn't get the error anymore. If you look at the last form picture I posted, there's a subform in the subform's footer. I was using the same query for the Record Source as one of the other tabs.

That initial query used the BeadTypeID.Value. I didn't need that in the sub-subform as it is linked on a different field. So, I just made a copy of that query, removed the BeadTypeID from it, saved, and changed the Record Source on the problem subform. Whew.

Taking stuff out until the problem went away really helped narrow my focus. I'll have to remember that tactic for the future. :)