I agree with you about consistency. But when I read a table name and the field name as "customers.address", it sounds kind of kludgy. When I see the table name and field as "customer.address" it makes more sense (as I am looking at the address of a specific customer). Plus, if you name the table "customer" you save many key strokes in the life-time of the application writing/maintaining <g>

>I had to google verbacular (interesting - try it) then realized it was a typo <g>
>
>Yeah, as I said it really doesn't matter if you are consistent. One of my partners completely sees it as you do.
>
>Plurals are funny in different languages. Weirdest ones I ran across were bahasa (Indonesian) where you just say the word twice - i.e. orang orang = "men" and Thai where there are qualifiers for every noun.
>
>I see dog five bodies. I have banana 10 combs. There are person 100 person.
>
>Not sure what they do naming databases in Thai. I wonder if the Indonesian version of .NET would rename your table CustomerCustomer <bg>
>
>>>> list/collection of clients be called clients
>>
>>I think it depends on how you say it, Charles.
>>One might say the client table - a place where any one client record would reside, just as one might say a guest house, a stamp collection, a bird house or a dessert table (to mix metaphors).
>>Someone else might say a table of clients, a collection of stamps, or a table of desserts and that person would probably call the table clients.
>>Some verbaculars don't use abstract nouns or collective nouns the way we do in most parts of the US.
>>So my wife, whose family spoke German (Schwabish) primarily when she was young says things like " two insurances" when referring to two insurance policies or "two breads" when referring to two loaves of bread.
>>She'd call it clients for sure.
>>I note that .NET "pluralizes" table names on its own volition in some cases and that drives me batty.