vbCrLf in a string

I have a program that I'm troubleshooting, and I have a bunch of strings that are as follows:

Quote:

---

bungcords = vbCrLf & "__ bungcords"

---

Also, I have a few parts like this:

Quote:

---

If CheckBox1.Checked = True Then
Input1 = vbCrLf & "__ " & txtInput1.Text
End If

---

Is that the proper syntax to be using? I'm not sure with this debugging stuff, because the program will run on my computer, but not on any others (with the Framework installed, of course). Thanks.

I can't see any problem in your code !!

But be aware that the new line comes before the text. If the control u are using have space for only one line, you will not see the text.

try adding \n as that is used for line breaks now in .NET

"Hello\n Chris"

should look like this in a texbox

Hello
Chris

no its not used in .NET ...its just in c++ and c# not in vb

Thanks for the responses! I'm working on the project right now. WHEN I get it working (I will if it's the last thing I do) I'll post back. Same thing goes if I have any more questions develop.

EDIT**

I can't seem to get the \n to work properly. For a buttons click event:

Quote:

---

TextBox1.Text = "This is some\n Text"

---

It Prints it exactly like that. Am I using that correct way, or am I missing something? With a couple quick glances at the Help, I'm still clueless (as usual for me with MS help...).

As PT Exorcist said, /n is not vb code. It only works with C++ and C#.

I see. I thought he was referencing the vbCrLf part. But that explains it then.

sorry I use both C# an VB so I get confused from time to time.

LOL :p

yes i at start thought we could use \n too but tested and it seemed not to work lol

Did you try:
ControlChars.NewLine
Or ControlChars.CrLf

Quote:

---

Originally posted by Dodgeram01

Is that the proper syntax to be using? I'm not sure with this debugging stuff, because the program will run on my computer, but not on any others (with the Framework installed, of course). Thanks.

---

That code should work no problem. Are you sure that your errors aren't caused by something else?

It's gotta be, because trying a few more of the changes still yields errors. Time to get out the fine tooth comb it sounds like...:(

Well, a little update. I solved the problem. On some accessory forms, I had them closing with just

Quote:

---

Close()

---

. I changed them to

Quote:

---

Me.Close()

---

and it now runs. Thanks for your help everyone, and I'm sorry that vbCrLf wasn't the issue. But I did learn some stuff, such as the ControlChars.NewLine commands.