>Hmmm, something to think about, for sure. And Sergey did already mention the performance degradation with updates. The table in question will not have heavy updates, except initially when the user is setting up their data (it's a codes table), so I think that performance-wise, we'll be ok using the varchars in this case. But, I'll definitely take this into consideration for other tables that I design. Thanks!
>
>~~Bonnie
>
No problemo. Unfortunately I've seen too many DB's where varchars were used way too much - down to varchar(1)!
Dan LeClair
www.cyberwombat.comSET RANT ON - The Wombat BlogLife isn’t a morality contest and purity makes a poor shield. - J. Peter MulhernDisclaimer: The comments made here are only my OPINIONS on various aspects of VFP, SQL Server, VS.NET, systems development, or life in general, and my OPINIONS should not be construed to be the authoritative word on any subject. No warranties or degrees of veracity are expressed or implied. Void where prohibited. Side effects may included dizziness, spontaneous combustion, or unexplainable cravings for dark beer. Wash with like colors only, serve immediately for best flavor.
