Thanks Chris.

John

>
>To My understanding,
>Varchar saves space as it only stores as many chars as are needed.
>But is slow if you need to change the data, as it needs to resize that field.
>
>Ive also found that whenever I pull a varchar from SQL Server, it is full of CHAR(0) in between each character, which i need to strip out.
>
>IMO, I would stick with Char(x) fields if you know the length they are going to need to be.
>Use VarChar for things like memo's