>Actually, I think this is a waste of time in xBase too. It makes sense with variables because xBase is weakly typed (meaning you can put any value into any variable), so a naming convention tells the developer what data type is expected in a variable. However, fields in tables are strongly typed, so there's no need to use a naming convention to tell you the expected data type; just look at the table structure.
>

I agree here, and I'm also not a fan of specifying scoping on all variables - I prefix PARAMETERS with "t", PUBLICs with "g" and PRIVATEs with "p" - IOW, things that might be affected by side-effects from assignment operations. Since most of what I do ends up LOCAL or a member property of something, it's unusual to see "g" or "p" in my code, especially since I've started doing AddProperty() against the _VFP or _SCREEN object to carry around my global objects in an app.