>Working on one of my projects I got a screen with 10 sec opening time. The reason was Active-X using in this form and it was frequently-used screen so even 10 sec was not accessible. So what I had to do? I wrote 'fantom' screen, loaded and hid it on application start (user can wait 10 sec starting app) and then during App flow I just showed and hid the screen, which is much faster. I want to say that there are a lot of ways to workaround.

Quoting myself:
"There are several dialogs that are built at the beginning of execution, rather than opened as needed, since they take time to build several of their controls."

These involve .ocx files, and it does speed up the system, by taking the hit at the beginning once, instead of every time those dialogs are opened.

The main form I mentioned has no .ocx controls.