Posts by codeorder

(img.located and slightly edited from: http://futiledemocracy.wordpress.com/tag/jesus/)

I went ahead with the On Error Resume Next and it met the requirements needed for me to accomplish my "previous" task.

Thanx for any and all input from the both of you; quite more informative than expected. :)

Reverend Jim, should I proceed with the On Error Resume Next or Not? Seems like the only clear.solution for this issue, other than a bunch of "GoTo" and tons of Try/Catches. AndAlso, thanx for code.sample, news2Me.

Thanks for the informative reply Oxiegen. :)

I basically need to run a Sub that will set values to TextBoxes with Ctype(someCoolForm.Controls("someCoolTextBox"),TextBox).Text="daniweb.com" and wanted to use the minimum amount of typing/lines to accomplish this, even if it throws an error in case a TextBox does not exist on a Form; since planning to use that Sub for multiple.Forms/.Apps.
.Using a Try/Catch, it will error on first error and go straight to the Catch part, which does Nothing for the remaining TextBoxes waiting in line for values, If they exist on a specified Form.

As for the On Error Resume Next, I think that it should stay as a .Net option, even if integrated from the previous non.Net Visual Basics. A very strong opinion from my point of view.

Regarding the "Have you looked at MessageBox()?":
I have and it does offer a few/or one extra option(s) above the MsgBox, though for testing, MsgBox is less time typing and quicker results. :)

Regarding my previous.post containing this:

As a human being, how old are you in the eyes of the heavens, if not counting the time spent sleeping without dreams?

I came to a conclusion.

Being a vb.noob as basically most of the vb.net world, I use the Try/Catch statement quite a bit for when it comes to errors, as the following.

        With Me
            .Text = "a"
            Try
                .Text += 1
            Catch ex As Exception
                MsgBox("error: " & ex.Message, MsgBoxStyle.Critical)
            End Try
            MsgBox("a")
            .Text = "b"
            Try
                .Text += 1
            Catch ex As Exception
                MsgBox("error: " & ex.Message, MsgBoxStyle.Critical)
            End Try
            MsgBox("b")
        End With

For the first time today, I attempted to use the On Error Resume Next and it returned the results I needed; less lines of code and only results if an error occured.

        On Error Resume Next
        With Me
            .Text = "a"
            .Text += 1
            MsgBox("a")
            .Text = "b"
            .Text += 1
            MsgBox("b")
        End With

My question is, even though quite clear to me:
For such lines of code as above, is the On Error Resume Next appropriate and can I move on to the next part of my.app with no worries, ever?
.thanx.in.adv,.Me.

bad day ?

Just stating fact, Nothing Else. :)

Fugg this ambiguous word, yo!!!(tough cookie to crack;D)

Foshizzle

Know the Brouhaha of the world and know their greed.

Thanks :)

What would codeorder do if this thread was never created?

I would not help out with the Thoughts of the Day, Nothing Else.

I am currently at a loss, for I cannot matiscate? the word mastication in a sentence. :'(

Honesty