>This discussion started around the variable scoping issues. I proposed that PUBLIC was a bad practise because it has potential side effects that are hard to track down later. One example I gave was an app that later is called by another app where a public var in the called app can cause problems with the calling app. It is very easy to totally eliminate this potential problem forever, simply NEVER USE PUBLIC VARIABLES and this problem will NEVER happen.

Sometimes a PUBLIC variable is necessary. For instance, if we "hard-code" our forms, it always seems that runtime won't byte until it is declared public. I wish someone could show me the light on that one! I am *slowly* moving to class containers for PUBLIC variable management. I am probably using 8 or 10 percent of the total paradigm - and still I suufer from synaptic overload. Maybe if I double up on my Gingko, it would move to 12%:-).