Hi All,
Im have a strange situation with SQL Server 2000. I am trying to paste this into a VARCHAR (8000):
However when I paste the above text into SQL Server I get this warning:
"The value you entered not consistent with the data type or length of the column."
I read on the web a little and discovered that somebody had this problem and they had used NVARCHAR instead which fixed it for them, this has not worked for myself though.
Does anyone have any idea what SQL is objecting to?
Thanks, Dave.
Im have a strange situation with SQL Server 2000. I am trying to paste this into a VARCHAR (8000):
Admittedly this is a long piece of text but running a little letter count application I know that it is only 1211 characters long.<aspanel id=pnlFlashBanner style=Z-INDEX: 104; LEFT: 288px; POSITION: absolute; TOP: 312pxrunat=server Height=112px Width=632px><OBJECT codeBase=http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,29,0height=100 width=600 classid=clsid27CDB6E-AE6D-11cf-96B8-444553540000 VIEWASTEXT><PARAM NAME=_cx VALUE=15875><PARAM NAME=_cy VALUE=2646><PARAM NAME=FlashVars VALUE=><PARAM NAME=Movie VALUE=MEB_Banner.swf><PARAM NAME=Src VALUE=MEB_Banner.swf><PARAM NAME=WMode VALUE=Window><PARAM NAME=Play VALUE=-1><PARAM NAME=Loop VALUE=-1><PARAM NAME=Quality VALUE=High><PARAM NAME=SAlign VALUE=><PARAM NAME=Menu VALUE=-1><PARAM NAME=Base VALUE=><PARAM NAME=AllowScriptAccess VALUE=always><PARAM NAME=Scale VALUE=ShowAll><PARAM NAME=DeviceFont VALUE=0><PARAM NAME=EmbedMovie VALUE=0><PARAM NAME=BGColor VALUE=><PARAM NAME=SWRemote VALUE=><PARAM NAME=MovieData VALUE=><PARAM NAME=SeamlessTabbing VALUE=1><embed src=MEB_Banner.swf quality=high pluginspage=http://www.macromedia.com/go/getflashplayertype=application/x-shockwave-flash width=600 height=100></embed></OBJECT></aspanel>
However when I paste the above text into SQL Server I get this warning:
"The value you entered not consistent with the data type or length of the column."
I read on the web a little and discovered that somebody had this problem and they had used NVARCHAR instead which fixed it for them, this has not worked for myself though.
Does anyone have any idea what SQL is objecting to?
Thanks, Dave.