Franco,
Thanks for the reply and link (I was about to use NText in one of the tables <s>).
I try to share as much code with the PPC guy as I can but unfoutunately he is lagging behind me and that can sometimes cause problems. When it comes to table design I hope that table structure can be exactly the same (or very similar) and that is why I am spending so much time on this now. After eating lunch (and reading your messages) I will go with the N prefix datatypes.

Thank you very much for spending time on this with me.

Sincerely,
Einar

>I think that in that link they are referring to what is supported by the .NET CF, not by SQLCE, which is another story.
>I don't know if the non-N-prefixed will be dropped in future, but take a look at this link, there is an important note at the top (and this regard SQL Server, not only the mobile version):
>
>http://msdn2.microsoft.com/en-us/library/ms191262.aspx
>
>If you have to create PPC and Desktop apps, I think it's better that you base your "apps design" using what is the "less" between the full .NET and the CF, and between SQL Server and SQL Mobile.
>For example, in VS2003, ppc apps can't use typed dataset. Well, if you start develop the PC app and create typed dataset, you can't use them in PPC development, so you'll may go in troubles.
>In VS2005 (I' ve not tried this yet) it seems that you can use typed dataset, and things are changed a lot, so take a look at the new features before decide.
>
>Franco
>
>
>
>>Franco,
>>Thanks for your reply. I am not doing a lot of work with the compact framework. I am in charge of the PC software and another guys is in charge of the PPC software. I started designing some tables needed on the PC side, but I know the PPC will need similar (sometimes exactly the same) table.
>>
>>Here is the link to the documentation I refered to when I said that I thought NET CF supported both data types with or without the N prefix:
>>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemdatasqldbtypeclasstopic.asp
>>
>>Would you agree that moving forward it is probably best to choose data types with the N prefix (NVarChar, etc.)? Do you think data types without the N prefix will at some point in the future be removed from MS SQL server? Maybe next version?
>>
>>Thanks for taking the time to discuss this with me.
>>
>>Einar
>>