Hi George,

>In your example, "tcOrder" tells me that it's a character string passed as a parameter. I see nothing wrong with the naming convention. However, if it were a field in a table, what would that tell me? Is it a datetime represented as a character string?

CORDER returns many hits in Google, some related to re-CORDING. CORD is a synonym for STRING. Why shouldn't there be a field tCorder or tCordER which is fully compliant with the Codebook naming convention for fields.

The problem with naming conventions is that most of them do not avoid collisions.