Ok, the way this works?
the master page load ONLY fires again WHEN you move to a different page - hence your comments about it only works when I move to a different page seems correct.
However WHILE you on that current page? Then post-backs can freely occur in the child page, but the master page load event does not trigger or fire again.
So, you need then to either mess around with code in the child page that changes the parent page.
However, one really simple way - and since you don't have to do this all that often?
Just in code navigate to the SAME page your currently on, and it will fire your master page load.
So, say the page was say SignupInfo.aspx?
Well, in your code - once you done your work - or whatever? then simple always navigate to where ever you want to go.
However, if you going to remain on the same page? Then navigate to the same page.
So, if you jump to the same page you are on, then master page load event will trigger. Now, in some cases, this simple idea might not be what you want, but often, this "rare" need to re-fresh the master page (and probably see the menu bar update) can save you having to adopt messy code try and modify master page from child. Now, for your welcome message to work? You might have to shove it into session(), and then on page load check for that session() value, and set the label to show the welcome text/msg you have.
Albert D. Kallal (Access MVP 2003-2017)
Edmonton, Alberta Canada