Ken,

SNIP
>
>I appreciate yor opinion. I am still debating on the "Table prefix" thing. The strongest arguments I still have for keeping it are:
>
>1 - always know what table a field belongs to - no chance for confusion
>2 - saves typing on joins since table refs/aliases are not needed
>3 - no chance of stomping on reserved words
>
>My only REAL concern is going against the "industry standard" grain, but interestingly, nobody has voiced an argument along that line.

Are there cases where your users view/manipulate any data (fields) directly, themselves? Such as browsing or tailoring reports or queries?
If there are, then I doubt that prefixes help them.

As regards "industry standards", I guess the lack of such an argument means that there is no standard for this - THANKFULLY! More and more we (developers) are being pushed into standard ways of doing things and it is nice that there are still a few areas where one's own creativity/preference can rule.

Cheers

>
>Thanks!