>The memory constraints are not so important today. IMHO, David's reason is much more important.
>
>Anyway, I don't see why using public vars would take more memory than using object properties. More likely, is the other way.

Hi Paul,

Here is the actual claim of MS regarding this matter:

" instead of using variables, you can reduce memory consumption, increase performance, and simplify programs. "

Simply because PUBLIC variables are always residing in the memory and is available in the entire application as compare to custom properties which are within the FORM only and are released when the FORM releases.

Same thing with #INCLUDE header files (for #DEFINE, #IF, #IFDEF etc.) which is recommended when you have constant values being used.


>
>Vlad
>
>>Yes, avoiding PUBLIC variables being declared is a good practice because of memory space constraints.