> > Hello!> > > > I just want to share some new thoughts regarding the title. If you are interested, read it here: http://www.junblogs.com/?p=484> > > > I know I am late with this as I believe a lot of members are already using this approach but for those who hasn't yet, then I hope it will be useful to them.> > > > http://www.junblogs.com/> > http://weblogs.foxite.com/sandstorm36/default.aspx> > http://www.coderisland.com/forum/viewforum.php?f=10> > Objects can also be protected from changes, which public vars cannot. You might want to demonstrate that aspect in your class. BTW, if you have a company table and a company object, "company.name" will become vague. I'd go with oCompany for the object name.> > Mike Yearwood> Microsoft MVP Visual FoxPro 2008, 2009> We have enough youth. We need a fountain of smart!> There may be many ways to skin a cat, but there are very few right ways to do it.

Yeah you right Mike.The prefix is not merely as a prefix, but to further confirm what type of data we are working.

USE Company IN 0
LOCATESCATTERNAME oCompany
? oCompany.Name
? oCompany.Address