> > I am!
> >
> > I have never found a scenario where a PUBLIC variable is the only solution. There is always an alternative and the alternative is always better.
> >
> > I have never understood why people seem to think that just anyone, wiith no knowledge or training, can write a computer system. This phenomenon doesn't occur in other businesses - no-one (sensible!) would dream of setting up as a Doctor, Dentist, Accountant or Lawyer, or even a Plumber or Electrician, with no expertise or knowledge whatever. Yet people who have no idea of how to design an application go right ahead and start writing code that they think they can then use to run their business!
> >
> > Personally I blame Microsoft in general and Visual Basic in particular....[g]
>
> before you come and try to attack people being lazy, without knowledge like you just did ....

>
> I have nothing against other views, I did as here because I want to see the Point but not by beeing told ... that everyone who uses PUBL Vars is "Lazy, Stupid, without knowledge" and should stay away from computer programming ...

Hi Thomas

Please don't take things personally. I'm hopeful Andy is not saying you personally are lazy or stupid. I agree with his opinion though. I believe most of the time, public vars are used badly, even to the point of putting lives at risk. It would be best to avoid them. Even when objects replace the public vars, nothing is done to protect the properties from changes, so there is little benefit. Most of the time, in my experience the programmers did not know there was any danger when they originally used them or it was just habit. Once they're used, one just has to be careful maintaining the code.

Mike Yearwood
www.foxridgesoftware.com
President: Toronto Ontario FoxPro User's Group