"Hugo Kornelis" <hugo@perFact.REMOVETHIS.info.INVALID> wrote in message
news:l5277213bpbjlcup0frbiqht8eii4j61mc@4ax.com...
> On Tue, 23 May 2006 18:55:52 -0300, Carlos Albert wrote:
>
>>Hello group,
>>
>>I have to convert some strings that I had on a Text field to Nvarchar. I
>>don't care if some data gets lost.
>>I tried this, but doesn't work because it's too long and complains about
>>it:
>>
>>UPDATE mytable
>>
>>SET mynVarChar= cast(myInfo as nvarchar(4000))
>>
>
> Hi Carlos,
>
> Is the column "mynVarChar" declared as nvarchar(4000) ???
>
> I could not reproduce this - until I tried what would happen if the
> column mynVarChar is shorter than 4000 positions.
>
> You can't just use nvarchar without explicit length in the CREATE TABLE
> statement, since the length will default to 1 in that case!
>
> --
> Hugo Kornelis, SQL Server MVP

On Tue, 23 May 2006 18:55:52 -0300, Carlos Albert wrote:

>Hello group,
>
>I have to convert some strings that I had on a Text field to Nvarchar. I
>don't care if some data gets lost.
>I tried this, but doesn't work because it's too long and complains about it:
>
>UPDATE mytable
>
>SET mynVarChar= cast(myInfo as nvarchar(4000))
>

On Wed, 24 May 2006 09:53:05 -0300, Carlos Albert wrote:

>Hello Hugo. First of anything, thanks for your answer.
>
>Yes, mynvarchar is an existing field, declared as nvarchar(4000)...