UserForm pops up when a cell = TRUE, don't show again once closed until a cell changes

[Lynx_TWO]

Good Morning!

Racking my head on this one: I created a basic user-form that is set to show when cell H1 = TRUE. Works great, looks great. However, when you click the command button on the userform to close (using the Unload command), it closes and then just pops up again because H1 still = TRUE. What I want it to do is close and not re-open unless any cells in the ranges A1:B10 or D1:D10 are changed after the userform has been closed.

This has to be easy, right?

Thanks so much in advance!

[mehmetcik]

Attach a sample workbook (not a picture or pasted copy). Make sure there is just enough data to demonstrate your need. Include a BEFORE sheet and an AFTER sheet in the workbook if needed to show the process you're trying to complete or automate. Make sure your desired results are shown, mock them up manually if necessary.

Remember to desensitize the data.

Click on GO ADVANCED and then scroll down to Manage Attachments to open the upload window.

[BadlySpelledBuoy]

Do you mean the userform shows when H1 is changed to TRUE or is there another process that looks if H1 = TRUE and opens the form if it is?

As per mehmetcik's post above, would be helpful to see the workbook so we can see it in context.

BSB

[Lynx_TWO]

Mocking it up now, will post

[Lynx_TWO]

OK, I'm an idiot. The mock-up worked just fine, so I went back and took a good look at my code on the Main Worksheet to trigger the userform,

Private Sub Worksheet_Change(ByVal Target As Range)

Turns out I had it nested inside another code which checks specific criteria in a loop, so every time I would close the userform, it didn't matter since it had become part of the loop.

Moved the userform trigger all the way to the bottom after the last End If and before End Sub, and now everything works as it should.

Jees man, I spent hours trying to figure out what the heck was going on. No wonder Google wasn't finding anything lol

Lesson learned! There should be a Best Practices or Dumb Mistakes list somewhere :P

[BadlySpelledBuoy]

Important thing is it's all sorted now and you've learned something.

You could have spent many more hours on it before finding the issue...

BSB

[Lynx_TWO]

True! I'll be sure to try isolating incidents in a mockup in the future. The tool I'm developing has just gotten really extensive, so it's getting easier and easier to make dumb mistakes :D

Thanks again!

-Dan

[BadlySpelledBuoy]

The tool I'm developing has just gotten really extensive, so it's getting easier and easier to make dumb mistakes :D

That's often how these things turn out. Solution there is meticulous planning before you even touch the keyboard and start building the thing!
Learned that lesson the hard way myself...

BSB