Another good argument I have heard for naming conventions applies more to SQL Server. SQL Server is not as tolerant as VFP when reserved words are used. With a naming convention that prefixes or postfixes field names, you are unlikely to run into a SQL Server reserved word in the future.

Of course, having said all that, I still don't use prefixes or postfixes. < g >

>Koos,
>You may find this starts a long and controversial thread. A couple of years ago Jim Nelson and someone else (can't remember who) had 'competing' articles in FPA on this subjec.
>
>We use a 2-letter prefix unique to each table in our apps and have found it extremely useful. One advantage is not having to repeat the table name in SQL-Select commands, and never running into fields with the same name. Another is that it helps us figure out code when we're updating or debugging apps we haven't worked on for a while.
>
>We use a 4-character code for all PKs - xxID (xx is the table prefix) and a 7-character code for all FKs, xx_ptID (xx is the present table prefix and pt is the parent table prefix). We also try to use the same field name (except for prefix) when we have 'matching' fields. For example a present app has 10 fields that are identical in Quote, OrderDetail and Estimate tables, and we use the same names in all 3 tables.
>
>Again, this is controversial and you'll have to figure out if it will work throughout your framework and team.
>JMHO
>Barbara