>
>I agree that keys need to be uniquely named. It's a shame that the M$ white paper didn't bridge conventions to keys primary and secondary.
>
>Do developers still make a combined primary key these days? {outside of SBT that is}
>
>__Stephen
Yes, some do...but they shouldn't. The PK should be totally meaningless to the data. It should not be something the user has to enter, nor should it be madeup of a combination of fields. I have a KB artilce on my website that discusses this.
While we're discussing standards, I have a standards document that I've been using for sometime. I'll try to post it on my web site in the next few days.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer