character truncation problem in database 2

[btween]

I have a page that enters received post values into an ms sql database. The problem is that I get some number like 000450 and upon insertion it is truncated to 450.

I have my db field set as nvarchar 50

am I using the wrong data type for this field?

how can I maintain all 6 numbers in the database?

thanks for your help

 

[dbomrrsm]

I thin it depends on how it is being passed in if a number is being passed in to an nvarchar it will get runcated but if text is passed in it stores it as text.

see examples:

declare @q nvarchar (50)
set @q = 004560
print @q

declare @p nvarchar (50)
set @p = '004560'
print @p

[blue]DBomrrsm[/blue]

[blue]Software code, like laws and sausages, should never be examined in production[/blue][black] - [/black][purple]Edward Tenner[/purple]

 

[donutman]

Something is wrong. It should not do that with a varchar field. The question of datatype depends upon what sort of text you are storing. Do you really need nvarchar rather than char or varchar?
I'm guessing that your front-end is causing the problem.
-Karl

[red] Cursors, triggers, user-defined functions and dynamic SQL are an axis of evil![/red]
[green]Life's uncertain...eat dessert first...www.deerfieldbakery.com[/green]

 

[miq]

HI,
I think DBomrrsm has raised a good point.

B.R,
miq

 

[donutman]

I think Domrrsm cooked-the-books on that example!
-Karl

[red] Cursors, triggers, user-defined functions and dynamic SQL are an axis of evil![/red]
[green]Life's uncertain...eat dessert first...www.deerfieldbakery.com[/green]

 

[dbomrrsm]

what do you mean Karl ?

[blue]DBomrrsm[/blue]

[blue]Software code, like laws and sausages, should never be examined in production[/blue][black] - [/black][purple]Edward Tenner[/purple]

 

[donutman]

[Blue]DECLARE[/Blue] @q [Blue]varchar[/Blue] [Gray]([/Gray]50[Gray])[/Gray]
[Blue]SET[/Blue] @q [Gray]=[/Gray] 004560
[Blue]PRINT[/Blue] @q

But you still maybe right, I simply don't know.
-Karl


[red] Cursors, triggers, user-defined functions and dynamic SQL are an axis of evil![/red]
[green]Life's uncertain...eat dessert first...www.deerfieldbakery.com[/green]