>We take a somewhat different approach in vfp...I agree, no antiquated "m." prefixes, but all locals have typing prefixes, and no field names ever do. As one or two others have noted, users often have access to tables/fields (through CR, for example), so we want very English-like naming conventions - no funny esoteric prefixes allowed...and generally only long and highly descriptive field names...

Yes, that will do the job also, and I will remember your point
about users seeing field names. I will be deploying FoxFire
full version and I if I remember correctly I can rename all of
the fields.

Peter