Excerpt for one char long fields and fixed size fields like serial numbers,
you should always use varchar instead of char on SQL-Server.
Because of internationalisation and localisation issues, an even better idea
would be to use nchar, nvarchar and ntext fields instead of char, varchar
and text fields.

Signature
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: http://cerbermail.com/?QugbLEWINF
> This is my first Access Project to develop, so I'm learning the ropes of
> dealing with SQL Server. One thing that cropped up is that the "char"
[quoted text clipped - 10 lines]
>
> Mick Ruthven
Mick Ruthven - 27 Jan 2006 16:58 GMT
Thanks, Sylvain! How about a bit more explanation of why the "n"-type fields
are best?
> Excerpt for one char long fields and fixed size fields like serial numbers,
> you should always use varchar instead of char on SQL-Server.
>
> Because of internationalisation and localisation issues, an even better idea
> would be to use nchar, nvarchar and ntext fields instead of char, varchar
> and text fields.
Sylvain Lafontaine - 27 Jan 2006 17:06 GMT
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/sq
l_dataencoding.asp
http://support.microsoft.com/default.aspx?scid=kb;en-us;322112

Signature
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: http://cerbermail.com/?QugbLEWINF
> Thanks, Sylvain! How about a bit more explanation of why the "n"-type
> fields
[quoted text clipped - 8 lines]
>> would be to use nchar, nvarchar and ntext fields instead of char, varchar
>> and text fields.
Mick Ruthven - 27 Jan 2006 17:53 GMT
Thanks again, Sylvain. You've made my learning process about this much
quicker.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/sq
l_dataencoding.asp
> http://support.microsoft.com/default.aspx?scid=kb;en-us;322112