Franco,
I haven't started reading SQL2005 documentation (mostly because I want customers to be able to use SQL2000).
According to the VS2003 documentation (SqlDbType Enumeration) it appears that both data types with and without N prefix are supported in .NET CF.

Do you use data types with the N prefix in your tables?
Could you please post a link to the information you refered to in your post?

Einar

>Hi Einar,
>in SQLCE (at least in 2005) I see only "N prefixed" datatypes: only nvarchar, ntext, ecc.
>so, I think, you have losed a week-end :))
>
>Franco
>
>
>>I have been pondering this all weekend. I can't decide if I should use a data type with the N prefix (i.e. NChar, NVarChar, NText, etc.) or if I should use a data type without the N prefix (i.e. Char, VarChar, Text, etc.).
>>
>>A string in .NET is always unicode, so that lead me to think that I should use a data type with the N prefix. Now I have to worry about tables in a PPC (SQL CE) and storage space is premium (even more premium than on a desktop PC). I would love to cut the storage cost in half by switching to a data type without the N prefix, but I I also want to remain flexible and extensible for the future. The application might be used outside the US, and I have always thought that was the biggest benefit of unicode.
>>
>>Any thoughts on this would be appreciated and please state if you use NVarChar or VarChar.
>>
>>Thanks,
>>Einar