Hi Brad,
Remember you can use local aliases to avoid typing long table names.
SELECT Inv.* FROM Invoices AS Inv or SELECT I.* FROM Invoices I
Polymorphism implies we use the same names in different things and rely on the context for meaning. I want to remember as few names as possible and use them consistently. The alias, object, or other context gives the meaning--I don't like explicit fieldnames that only apply to one table. Of course, in some joins, I have to use the "Name AS SpecificName" construct to avoid "_A" being added to the name.

>For what it's worth, my field naming conventions are the same as Walter Meester's, who gave you his opinions in the thread.
>
>The main reason I like the unique field names in a database is because I don't have to do a "table." prefix in front of every #*&@! field, especially in a query. A SQL-SELECT is much easier to write.
>
>--Brad