> > In addition to the Hungarian notation, i would suggest making field names unique across all tables within an application so that any queries created using "*" for the fields definitions yields field names matching the original table names (field1, field2, etc.) and not VFP generated names (field1_a, field 1_b, field2_a, field2_b, etc.). This is especially useful for creating on-the-fly queries.
>
> I strongly disagree with this advice. If two fields in different tables represent that same thing, they should have the same name.
>
> In a query, you resolve any ambiguity by listing the fields you need and using the AS clause to give them appropriate names.
>
> Tamar

What a field name represents is a matter of perspective. A PK in a company table is not the same as a PK in an invoice table. Should they both be called PK? EmployeeID in two different tables may be what you are referring to, but there is no harm in Sal_EmpID for the sales table representation of employee versus Emp_ID in the employee table. I've done both and don't see there is much different between the two except that I rather like not getting my hands slapped by the computer when I don't add the alias prefix.

Mike Yearwood