Hi,
>The whole VFP is cached and even the OS is somehow priority-minded
>-> if you start VFP application and run it - first time it is slower but the second time or more it is much faster. But let your app stay unused for a while (an hour or more) and click f.ex a menu or a form to start again and it is slooooowwww until it is cached again.

from my timings the class definitions get cached, and the vcx/scx files don't need to be accessed again. What you are describing is the out-swapping of the processes' memory to disk again - you friendly OS at work. Nearly the same effect can be reached by giving VFP a very small background memsize and switching active windows.

HTH

thomas