> >
> > I guess you talking about mixing up names !? e.g. it is easier to mixup the cFirstName with "FirstName" or what!?
> >
> > as I said earlier one should PREFIX the PUBL Vars so 1) you cant mix em e.g. with DBF Field, You always know that the VAR here is a PUBL one ...
> >
> > e.g.
> > PUBL cPBLFirstName
>
> No, I talk about possibilities to store the field value in wrong variable. OK you prefix your PUBLIC variables with cPBL*, but what is the guarantee that the developer that comes AFTER you to work/maintain that application will do the same? If He/She need to store the value of that field in the variable that should be visible from now on until the routine finishes its job, He/She easily could do this:

you know im only talking about PUBL VARS vs OOP [Kinda publ vars]

and the exact same thing you stated is true for the OOP too, if something went wrong and someone stores wrong result somethere ... the same thing will happen in both approach !?

And one MORE Point as I stated pefore PUBL Vars should only defined in ONE Place ... so such a case
as you mentioned could not happen.

If you dont follow some rules ... it doesnt matter with codeing style you use .. things will go wrong anyway ....