CR & Tab in VB 2005 Textbox

[AWW]

Using Textbox.Text = "123" & CStr(13) & "456"
I expect 2 lines on the screen but get 1 line with 13 in it.
It worked once in a RichTextBox but then stopped.
I just want to display aligned tabular data on the screen using CR &
Tabs to create data columns.
I am an old programmer but .Net novice.<g>
Help.

[Lloyd Sheen]

"AWW" wrote in message news:m2******** *************** *********@4ax.c om...

Using Textbox.Text = "123" & CStr(13) & "456"
I expect 2 lines on the screen but get 1 line with 13 in it.
It worked once in a RichTextBox but then stopped.
I just want to display aligned tabular data on the screen using CR &
Tabs to create data columns.
I am an old programmer but .Net novice.<g>
Help.

You may want to use the following constant under System.Environm ent

first is System.Environm ent.NewLine. This will ensure that you have the
correct setting for the newline character (no matter where it runs).

There is also a VBCRLF constant which can be used but is not really Dot.Net

Secondly (and gone if you use the above) the CStr is converting as you saw
to a string with that value. I can only suggest that you don't use any of
the old VB functions and go with straight Dot.Net. In the long run this
will make things easier and more consistant.

Lloyd Sheen

[Michel Posseth [MCP]]

First make sure the textbox`s multiline property is set to true

and maybe you would findit easier to use the handy VB contstants

VbCr ( cariage return )
VbCrlf ( cariage return linefeed )
VbTab ( tab )
regards

Michel

<AWWschreef in bericht news:m2******** *************** *********@4ax.c om...

Using Textbox.Text = "123" & CStr(13) & "456"
I expect 2 lines on the screen but get 1 line with 13 in it.
It worked once in a RichTextBox but then stopped.
I just want to display aligned tabular data on the screen using CR &
Tabs to create data columns.
I am an old programmer but .Net novice.<g>
Help.

[\(O\)enone]

AWW wrote:

Using Textbox.Text = "123" & CStr(13) & "456"
I expect 2 lines on the screen but get 1 line with 13 in it.

I think the function you're looking for is Chr(), not CStr().

But anyway, you're much better off using vbCrLf instead:

\\\
Textbox.Text = "123" & vbCrLf & "456"
///

--

(O)enone

[Armin Zingler]

<AWWschrieb

Using Textbox.Text = "123" & CStr(13) & "456"
I expect 2 lines on the screen but get 1 line with 13 in it. It
worked once in a RichTextBox but then stopped.
I just want to display aligned tabular data on the screen using CR &
Tabs to create data columns.
I am an old programmer but .Net novice.<g>
Help.

I guess you know that you wanted to write Chr(13) instead of CStr(13). :-)

Or use vbCr instead.
Armin

[Michel Posseth [MCP]]

There is also a VBCRLF constant which can be used but is not really
Dot.Net

Secondly (and gone if you use the above) the CStr is converting as you saw
to a string with that value. I can only suggest that you don't use any of
the old VB functions and go with straight Dot.Net. In the long run this
will make things easier and more consistant.

Lloyd Sheen

Huh ???
Well read this

http://www.codeproject.com/useritems/novbruntimeref.asp

and read my responses

There is nothing old or outdated or whatever in the Microsoft Visual Basic
..NET Runtime

Just my thoughts regarding this mather

regards

Michel Posseth

"Lloyd Sheen" <[e-mail] in bericht
news:46******** *************** ***********@mic rosoft.com...

>
"AWW" wrote in message news:m2******** *************** *********@4ax.c om...

>Using Textbox.Text = "123" & CStr(13) & "456"
I expect 2 lines on the screen but get 1 line with 13 in it.
It worked once in a RichTextBox but then stopped.
I just want to display aligned tabular data on the screen using CR &
Tabs to create data columns.
I am an old programmer but .Net novice.<g>
Help.

You may want to use the following constant under System.Environm ent

first is System.Environm ent.NewLine. This will ensure that you have the
correct setting for the newline character (no matter where it runs).

There is also a VBCRLF constant which can be used but is not really
Dot.Net

Secondly (and gone if you use the above) the CStr is converting as you saw
to a string with that value. I can only suggest that you don't use any of
the old VB functions and go with straight Dot.Net. In the long run this
will make things easier and more consistant.

Lloyd Sheen

[Lloyd Sheen]

"Michel Posseth [MCP]" <MS**@posseth.c omwrote in message
news:uh******** ******@TK2MSFTN GP02.phx.gbl...

>

>There is also a VBCRLF constant which can be used but is not really
Dot.Net

Secondly (and gone if you use the above) the CStr is converting as you
saw to a string with that value. I can only suggest that you don't use
any of the old VB functions and go with straight Dot.Net. In the long
run this will make things easier and more consistant.

Lloyd Sheen

Huh ???
Well read this

http://www.codeproject.com/useritems/novbruntimeref.asp

and read my responses

There is nothing old or outdated or whatever in the Microsoft Visual Basic
.NET Runtime

Just my thoughts regarding this mather

regards

Michel Posseth

"Lloyd Sheen" <[e-mail] in bericht
news:46******** *************** ***********@mic rosoft.com...

>>
"AWW" wrote in message news:m2******** *************** *********@4ax.c om...

>>Using Textbox.Text = "123" & CStr(13) & "456"
I expect 2 lines on the screen but get 1 line with 13 in it.
It worked once in a RichTextBox but then stopped.
I just want to display aligned tabular data on the screen using CR &
Tabs to create data columns.
I am an old programmer but .Net novice.<g>
Help.

You may want to use the following constant under System.Environm ent

first is System.Environm ent.NewLine. This will ensure that you have the
correct setting for the newline character (no matter where it runs).

There is also a VBCRLF constant which can be used but is not really
Dot.Net

Secondly (and gone if you use the above) the CStr is converting as you
saw to a string with that value. I can only suggest that you don't use
any of the old VB functions and go with straight Dot.Net. In the long
run this will make things easier and more consistant.

Lloyd Sheen

Sorry what I meant was to keep the code Dot.Net you would use the functions
that are provide for each object. I do this since I use both VB and C# and
sometimes I need to use code (not enough for a seperate assembly) and if I
use the Dot.Net functions provided by the objects rather than the VB it is
easier to convert since it is mostly getting rid of ending semi colons and
changing square brackets into regular brackets (and the other stuff of
course).

I just find that this way (even though VB will not disappear , and I bought
a copy of VB1 in Long Beach the day it was first available so I have been
using VB for quite some time (I guess that was 91)).

Just my 2 cents

Lloyd Sheen

[AWW]

Yes, multiline is True in both RichTextBox & TextBox and
both VbCr/VBTab work in RichTextBox but only VbTab in TextBox.
I can rewrite the whole box but would like to rewrite individual lines
and cannot find any way to set a position for the rewrite.
Thanks - so far.

On Thu, 21 Jun 2007 20:38:04 +0200, "Michel Posseth [MCP]"
<MS**@posseth.c omwrote:

>
First make sure the textbox`s multiline property is set to true

and maybe you would findit easier to use the handy VB contstants

VbCr ( cariage return )
VbCrlf ( cariage return linefeed )
VbTab ( tab )
regards

Michel

<AWWschreef in bericht news:m2******** *************** *********@4ax.c om...

>Using Textbox.Text = "123" & CStr(13) & "456"
I expect 2 lines on the screen but get 1 line with 13 in it.
It worked once in a RichTextBox but then stopped.
I just want to display aligned tabular data on the screen using CR &
Tabs to create data columns.
I am an old programmer but .Net novice.<g>
Help.

[\(O\)enone]

Lloyd Sheen wrote:

Sorry what I meant was to keep the code Dot.Net you would use the
functions that are provide for each object. I do this since I use
both VB and C# and sometimes I need to use code (not enough for a
seperate assembly) and if I use the Dot.Net functions provided by the
objects rather than the VB it is easier to convert since it is mostly
getting rid of ending semi colons and changing square brackets into
regular brackets (and the other stuff of course).

There's nothing stopping you referencing Microsoft.Visua lBasic.dll and using
the functions within it from C#, you know! :)

--

(O)enone

[Michel Posseth [MCP]]

Lloyd

Did you now that you can just set a reference to Microsoft.Visua lBasic.dll
in a C# project and then use all the handy shortcuts in C# as well

And no you then not have a extra dependancy as we code on the framework and
the Microsoft.Visua lBasic.dll is part of the framework
regards

Michel

"Lloyd Sheen" <[e-mail] in bericht
news:7C******** *************** ***********@mic rosoft.com...

>
"Michel Posseth [MCP]" <MS**@posseth.c omwrote in message
news:uh******** ******@TK2MSFTN GP02.phx.gbl...

>>

>>There is also a VBCRLF constant which can be used but is not really
Dot.Net

Secondly (and gone if you use the above) the CStr is converting as you
saw to a string with that value. I can only suggest that you don't use
any of the old VB functions and go with straight Dot.Net. In the long
run this will make things easier and more consistant.

Lloyd Sheen

Huh ???
Well read this

http://www.codeproject.com/useritems/novbruntimeref.asp

and read my responses

There is nothing old or outdated or whatever in the Microsoft Visual
Basic .NET Runtime

Just my thoughts regarding this mather

regards

Michel Posseth

"Lloyd Sheen" <[e-mail] in bericht
news:46******* *************** ************@mi crosoft.com...

>>>
"AWW" wrote in message
news:m2****** *************** ***********@4ax .com...
Using Textbox.Text = "123" & CStr(13) & "456"
I expect 2 lines on the screen but get 1 line with 13 in it.
It worked once in a RichTextBox but then stopped.
I just want to display aligned tabular data on the screen using CR &
Tabs to create data columns.
I am an old programmer but .Net novice.<g>
Help.

You may want to use the following constant under System.Environm ent

first is System.Environm ent.NewLine. This will ensure that you have the
correct setting for the newline character (no matter where it runs).

There is also a VBCRLF constant which can be used but is not really
Dot.Net

Secondly (and gone if you use the above) the CStr is converting as you
saw to a string with that value. I can only suggest that you don't use
any of the old VB functions and go with straight Dot.Net. In the long
run this will make things easier and more consistant.

Lloyd Sheen

Sorry what I meant was to keep the code Dot.Net you would use the
functions that are provide for each object. I do this since I use both VB
and C# and sometimes I need to use code (not enough for a seperate
assembly) and if I use the Dot.Net functions provided by the objects
rather than the VB it is easier to convert since it is mostly getting rid
of ending semi colons and changing square brackets into regular brackets
(and the other stuff of course).

I just find that this way (even though VB will not disappear , and I
bought a copy of VB1 in Long Beach the day it was first available so I
have been using VB for quite some time (I guess that was 91)).

Just my 2 cents

Lloyd Sheen