>
>
>The only field naming standards I use are for the primary key, which is always Table + Id, so for Employee.Dbf, it is EmployeeId. This field name is used in all tables that need a reference to the Employee.

I agree that keys need to be uniquely named. It's a shame that the M$ white paper didn't bridge conventions to keys primary and secondary.

Do developers still make a combined primary key these days? {outside of SBT that is}

__Stephen