New lines in textarea

I need to be able to strip out newline characters from data stored in a
textarea, but I've been unable to locate data so far that tells me how
newlines/carriage returns are stored in SQL Server. Any help on this
is greatly appreciated.CHAR(13)+CHAR(10)
http://www.aspfaq.com/2188
<Joiey.Seeley@.gmail.com> wrote in message
news:1131462555.249672.14910@.g47g2000cwa.googlegroups.com...
>I need to be able to strip out newline characters from data stored in a
> textarea, but I've been unable to locate data so far that tells me how
> newlines/carriage returns are stored in SQL Server. Any help on this
> is greatly appreciated.
>|||You can run the following statements to remove CRLFs from a column within a
table
update testtable set col1 = REPLACE ( col1 , char(10) , '' )
update testtable set col1 = REPLACE ( col1 , char(13) , '' )
testtable is your table and col1 is the column you want to do the replace on
.
Hope this helps
--
Adam J Warne, MCDBA
"Joiey.Seeley@.gmail.com" wrote:

> I need to be able to strip out newline characters from data stored in a
> textarea, but I've been unable to locate data so far that tells me how
> newlines/carriage returns are stored in SQL Server. Any help on this
> is greatly appreciated.
>|||I tried to use this method on a TEXT field using the following:
update support_incident set problem = REPLACE ( problem , char(10) , '' )
update support_incident set col1 = REPLACE ( problem , char(13) , '' )
Got this error message:
Server: Msg 8116, Level 16, State 1, Line 1
Argument data type text is invalid for argument 1 of replace function.
Server: Msg 8116, Level 16, State 1, Line 2
Argument data type text is invalid for argument 1 of replace function.
--
Ray
How do you remove the CRLFs from a text field?
"Adam Warne" wrote:
> You can run the following statements to remove CRLFs from a column within
a
> table
> update testtable set col1 = REPLACE ( col1 , char(10) , '' )
> update testtable set col1 = REPLACE ( col1 , char(13) , '' )
> testtable is your table and col1 is the column you want to do the replace
on.
> Hope this helps
> --
> Adam J Warne, MCDBA
>
> "Joiey.Seeley@.gmail.com" wrote:
>|||http://www.aspfaq.com/2445
"Ray" <ray.smith@.loislaw.com> wrote in message
news:E1FD569C-3F54-42FB-8B45-8C28B04883A5@.microsoft.com...
>I tried to use this method on a TEXT field using the following:
> update support_incident set problem = REPLACE ( problem , char(10) , '' )
> update support_incident set col1 = REPLACE ( problem , char(13) , '' )
> Got this error message:
> Server: Msg 8116, Level 16, State 1, Line 1
> Argument data type text is invalid for argument 1 of replace function.
> Server: Msg 8116, Level 16, State 1, Line 2
> Argument data type text is invalid for argument 1 of replace function.
> --
> Ray
> How do you remove the CRLFs from a text field?
> "Adam Warne" wrote:
>

New line in column?

Is it possible?
Sp1 said:
New Lines in Expressions
Previously, expressions had to be contained on a single line. With
SP1, expressions can include a newline character. New line characters
include carriage return (CR), line feed (LF), carriage return and
line feed (CRLF), paragraph separator (Unicode 2029), and line
separator (Unicode 2028). The newline characters are replaced with a
space when the report is processed.
But I can't use it.
Please help me!
--
Composed with Newz Crawler 1.7 http://www.newzcrawler.com/Could you please post an example of how you're using it?
--
Ravi Mumulla (Microsoft)
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Sean.Xiao" <ydxiao@.suntowntech.com> wrote in message
news:ufUQ64dhEHA.1656@.TK2MSFTNGP09.phx.gbl...
> Is it possible?
> Sp1 said:
> New Lines in Expressions
> Previously, expressions had to be contained on a single line. With
> SP1, expressions can include a newline character. New line characters
> include carriage return (CR), line feed (LF), carriage return and
> line feed (CRLF), paragraph separator (Unicode 2029), and line
> separator (Unicode 2028). The newline characters are replaced with a
> space when the report is processed.
> But I can't use it.
> Please help me!
> --
> Composed with Newz Crawler 1.7 http://www.newzcrawler.com/|||These textbox expressions/values were entered using the expression editor.
The first item, in the examples, is the textbox expression/value while the
second is how it should render. Hopefully these will point you the right
direction for using VB constants in expressions.
Example 1
--
="The brown fox jumped" & vbcrlf & "over the fence
The brown fox jumped
over the fence
Example 2
--
The brown fox jumped
over the fence
The brown fox jumped
over the fence
Example 3
--
="The brown fox jumped" &
" over the fence"
The brown fox jumped over the fence
For more information about constants see Visual Basic Language Reference,
Print and Display Constants:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vblr7/html/vamscmiscellaneousconstants.asp
--
Bruce Johnson [MSFT]
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Sean.Xiao" <ydxiao@.suntowntech.com> wrote in message
news:ufUQ64dhEHA.1656@.TK2MSFTNGP09.phx.gbl...
> Is it possible?
> Sp1 said:
> New Lines in Expressions
> Previously, expressions had to be contained on a single line. With
> SP1, expressions can include a newline character. New line characters
> include carriage return (CR), line feed (LF), carriage return and
> line feed (CRLF), paragraph separator (Unicode 2029), and line
> separator (Unicode 2028). The newline characters are replaced with a
> space when the report is processed.
> But I can't use it.
> Please help me!
> --
> Composed with Newz Crawler 1.7 http://www.newzcrawler.com/|||2004-08-20 00:32:50
"Bruce Johnson [MSFT]" <brucejoh@.online.microsoft.com> wrote in
message
<udj2toghEHA.556@.TK2MSFTNGP10.phx.gbl>
> These textbox expressions/values were entered using the expression
editor.
> The first item, in the examples, is the textbox expression/value
while the
> second is how it should render. Hopefully these will point you the
right
> direction for using VB constants in expressions.
>
> Example 1
> --
> ="The brown fox jumped" & vbcrlf & "over the fence
>
> The brown fox jumped
> over the fence
>
> Example 2
> --
> The brown fox jumped
> over the fence
>
> The brown fox jumped
> over the fence
>
> Example 3
> --
> ="The brown fox jumped" &
> " over the fence"
>
> The brown fox jumped over the fence
>
> For more information about constants see Visual Basic Language
Reference,
> Print and Display Constants:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-
us/vblr7/html/vamscmiscellaneousconstants.asp
>
> --
> Bruce Johnson [MSFT]
> Microsoft SQL Server Reporting Services
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
>
> "Sean.Xiao" <ydxiao@.suntowntech.com> wrote in message
> news:ufUQ64dhEHA.1656@.TK2MSFTNGP09.phx.gbl...
> > Is it possible?
> >
> > Sp1 said:
> >
> > New Lines in Expressions
> >
> > Previously, expressions had to be contained on a single line.
With
> > SP1, expressions can include a newline character. New line
characters
> > include carriage return (CR), line feed (LF), carriage return and
> > line feed (CRLF), paragraph separator (Unicode 2029), and line
> > separator (Unicode 2028). The newline characters are replaced
with a
> > space when the report is processed.
> >
> > But I can't use it.
> >
> > Please help me!
> > --
> > Composed with Newz Crawler 1.7 http://www.newzcrawler.com/
--
Composed with Newz Crawler 1.7 http://www.newzcrawler.com/|||Ok,Thanks Bruce.
--
Composed with Newz Crawler 1.7 http://www.newzcrawler.com/

New Job Unable to Copy 200 Line Code Into Command Section

I have a SQL Server 2000 database, I created a new job but I am unable to
copy the 200 lines of code that I created into the command section of the job.
Is there away to expand the New Job Command section?
I cannot use another job step to resolve this issue because I have alot
variables and a cursor used in this job.
This problem is resolve in SQL Server 2005.
Please help me resolve this problem for SQL Server 2000.
Thank You,Joe K. wrote:
> I have a SQL Server 2000 database, I created a new job but I am unable to
> copy the 200 lines of code that I created into the command section of the job.
> Is there away to expand the New Job Command section?
> I cannot use another job step to resolve this issue because I have alot
> variables and a cursor used in this job.
> This problem is resolve in SQL Server 2005.
> Please help me resolve this problem for SQL Server 2000.
> Thank You,
>
200 lines of code in a single job step? That's just insane. Put that
code into a stored procedure, and then use a single EXEC statement in
the job step.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||I fully agree with Tracy. If you, for some strange reason, don't want to do this, I believe the
limit is a bit higher at the TSQL level (i.e., the GUI is the limiting factor), so you could have
some more by using sp_add_jobstep.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message news:45BA5D73.3080102@.realsqlguy.com...
> Joe K. wrote:
>> I have a SQL Server 2000 database, I created a new job but I am unable to copy the 200 lines of
>> code that I created into the command section of the job.
>> Is there away to expand the New Job Command section? I cannot use another job step to resolve
>> this issue because I have alot variables and a cursor used in this job.
>> This problem is resolve in SQL Server 2005.
>> Please help me resolve this problem for SQL Server 2000.
>> Thank You,
>>
> 200 lines of code in a single job step? That's just insane. Put that code into a stored
> procedure, and then use a single EXEC statement in the job step.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com

New Job Unable to Copy 200 Line Code Into Command Section

I have a SQL Server 2000 database, I created a new job but I am unable to
copy the 200 lines of code that I created into the command section of the job.
Is there away to expand the New Job Command section?
I cannot use another job step to resolve this issue because I have alot
variables and a cursor used in this job.
This problem is resolve in SQL Server 2005.
Please help me resolve this problem for SQL Server 2000.
Thank You,
Joe K. wrote:
> I have a SQL Server 2000 database, I created a new job but I am unable to
> copy the 200 lines of code that I created into the command section of the job.
> Is there away to expand the New Job Command section?
> I cannot use another job step to resolve this issue because I have alot
> variables and a cursor used in this job.
> This problem is resolve in SQL Server 2005.
> Please help me resolve this problem for SQL Server 2000.
> Thank You,
>
200 lines of code in a single job step? That's just insane. Put that
code into a stored procedure, and then use a single EXEC statement in
the job step.
Tracy McKibben
MCDBA
http://www.realsqlguy.com

New Job Unable to Copy 200 Line Code Into Command Section

I have a SQL Server 2000 database, I created a new job but I am unable to
copy the 200 lines of code that I created into the command section of the jo
b.
Is there away to expand the New Job Command section?
I cannot use another job step to resolve this issue because I have alot
variables and a cursor used in this job.
This problem is resolve in SQL Server 2005.
Please help me resolve this problem for SQL Server 2000.
Thank You,Joe K. wrote:
> I have a SQL Server 2000 database, I created a new job but I am unable to
> copy the 200 lines of code that I created into the command section of the
job.
> Is there away to expand the New Job Command section?
> I cannot use another job step to resolve this issue because I have alot
> variables and a cursor used in this job.
> This problem is resolve in SQL Server 2005.
> Please help me resolve this problem for SQL Server 2000.
> Thank You,
>
200 lines of code in a single job step? That's just insane. Put that
code into a stored procedure, and then use a single EXEC statement in
the job step.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||I fully agree with Tracy. If you, for some strange reason, don't want to do
this, I believe the
limit is a bit higher at the TSQL level (i.e., the GUI is the limiting facto
r), so you could have
some more by using sp_add_jobstep.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message news:45BA5D73.3080102@.realsqlguy.co
m...
> Joe K. wrote:
> 200 lines of code in a single job step? That's just insane. Put that c
ode into a stored
> procedure, and then use a single EXEC statement in the job step.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com