>>Screen opening should be seamless (let say less than 2-3 sec). There are couple ways to split bulky queries which can delay opening, so experienced programmer shouldn't come up with a screen opening minutes and hours.
>
>I have a system for whom the main form take about 1 minute a piece to open (multiple instantiations possible) consisting mainly of a 10 page pageframe, with dynamically built grids on every page and subpages (with grids) on some of those. The data is filled from a dynamically built SELECT. 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. The total time taken to open this system on a mid-sized machine is about 1.5 to 2 minutes.
>
>We have analysed this code to see where the bottlenecks are. The answer - the actual instantiation of object by VFP. Not that an individual instantiation takes so long in and of itself, but that this quantity of objects have been made part of the system requirements.
>
>In short, you will find the occasional circumstance that system performance will be hampered, but compared to my other projects, I can reasonable say that this kind of situation is rare.

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.