Hi Koos,

FYI, a lot of database design tools force unique field names when scripting the database from an entity model so it's not a bad habit to get into. I can't say that I have strong feelings about it one way or the other, however, the table name will generally give you the information you need about a specific field, for example, "employee.name" is obviously the employee name, where "employee.emplname" seems redundant.

I do like to preface primary key columns and foreign key columns with "pk" and "fk" respectively, with the name of the rest of the column for foreign keys a pointer to the table, for example, "fkaddress" would be a foreign key linked to an address table.

>We are thinking in our shop to introduce a field naming convention that gives every table in each application a 2 letter code and that is the suffix for each fieldname, making all fieldnames unique.