Yeah, you might need to try using the Timer trick. Just load the bare essentials in the OnLoad or OnOpen events and put everything else in the Timer event after like 200 ms.

In my version and forms, nothing is displayed until after the Form_Current procedure has completed. You might try a breakpoint at the end of the Current procedure and see what happens.

Richard I forgot to mention that I did have it on the timer. But I didn’t think to move the bulk of the code to that trigger. Thanks! I’ll try it.

Thomas  Me looking to see how to add a Breakpoint!

Richard It worked!!! Amazing!

Ryan Click in the left margin of the code window, by the by the first line of code that you want to be paused.  You should see the line highlighted in red once the breakpoint is set.

Yeah, my forms all run better using that Timer trick... and you can SEE what's happening.

My forms do a lot of checking to make sure all the ducks are in order before progressing. One bad duck and the form closes down on Open.
I think the timer is best used to repetitive checking of conditions. One of my many bits of code in the Timer procedure checks to see if the administrator wants to shut down the entire system/network for some reason.

As to Ryan's specific problem, I can't see how what he was trying to do in Open/Load/Current wouldn't work. I do a lot of it in setting my own defaults that are more complicated than what the form property allows for as a simple value or expression. As well as showing all the procedures that ran in Open, Load and Current.  If the form closes down or hides and goes to another form, then maybe a "Continue" command button is in order (if the form should be closing down)? Seeing what happens with the breakpoint will help figure that out. As an alternative, you can place a Stop (before the End) at the end of Current procedure, and then just F8 to execute the next line of code.