>The only good reason I can think of to use a character based primary key is that it allows for the use of concatinated keys. This ability doesn't seem to out-weight the performance issues so why would I ever use a character based primary key? Am I missing the boat here? Is there some hidden advantage to it? If not, why do most all of the frameworks I have looked at default to it?
Most SQL Server based applications uses Integer because of the Identity clause. That said, if you want scalability, better of using Integer.
JESS S. BANAGA
Project Leader - SDD division
...shifting from VFP to C#.Net
CHARISMA simply means: "Be more concerned about making others feel good about themselves than you are in making them feel good about you."
