>Ever wonder when you make a typo in a SQL command putting a name of a table which does not exist and end up with a message like this:
>
>"The multi-part identifier "Client.AddDate" could not be bound."
>
>Where does this multi-part terminology come from? Something like "The table Client could not be found." or similar would be better I think.

I don't think SQL can know that the first part of the identifier was neccessarily intended to refer to a table ?
This lists the reasons:http://msdn.microsoft.com/en-us/library/cc645618.aspx