>It seems that each instance of my VFP application take less then 10MB RAM at start. It is almost independent of exe size (I tested sizes between 5-35MB).
>Use of memory grows when (after app starting) user runs my app forms.
>So it seems that successively creating objects while application is running may have greater influence on memory consumption than exe size.

I think good parts of the exe size come from the included files (vcxes and such), and their memo bloat (specially vcxes). A significant chunk of that is just dead blocks which never get used.

Memory use would rather be influenced by number and size of buffers, number of variables and, among them, specially objects. One good thing here is that OOP brought the good habit of not using public variables - easier to track, and you don't have a zillion of them taking up memory while your exe runs. Besides, I think keeping them as object properties gets us some speed - the table of names is split into few shorter ones (i.e. one per object and per contained object) so VFP should probably find one property value faster than one variable in a list of 500.