I haven't used field naming conventions for sometime, except for primary and foreign keys. I don't use Hungarian Notatation for variables (what we use in VFP) in .Net because it's not recommended. In fact, Hungarian Notation has generally fallen out of favor outside VFP. In strict typed languages such as .Net, it's easy to see the data type where it's defined.

>Now more and more of us are using more than one development language and/or database environment, I would be interested to know what you developers out there are doing regarding continuing the 'established' VFP standard of prefixing field names with the first letter of the datatype (c for character, n for numeric, l for logical, etc.) when you are working with other software.
>
>I am so used to it now that cFirstName, cSurname, cAddress1, etc. come more naturally to me than firstname, surname, address1... The more I look at other developers' work, or on-line demos in other languages, I have not noticed the convention used anywhere else apart from the VFP community. It's a pity it hasn't been adopted more widely. Is it used anywhere else?
>
>So...
>Are you keeping up the standard, and applying it to other development environments (ie. spreading the word, and the advantages)?
>Are you keeping up the standard for VFP only, but not for SQL-Server, C#, VB.NET, PHP, etc.?
>Have you abandoned (or not adopted) the notation in VFP because no-one else outside of VFP uses it?
>
>Any thoughts would be appreciated.
>
>
>Alan