> >
> > 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 because of 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
>
>
>
That would in my coding style not be sal_empid. It would be Sal.empid where Sal would be a table alias for Salaries or some such table name.
The column names should IMO not be prefixed with som abbereviated table name. If a table reference id needed for clarity, it's easily added by using Tablealias.columnname
I don't use a data type prefix either even though that's recommended in VFP's documentation, and is a fairly widespread custom in the Xbase world.
-Anders
-Anders