Vb.net skipping lines code

Question

0.00/5 (No votes)

See more:

Hi I have a problem with vb. The program skips lines of code.
It works in another program i did but in this program it doesn't work

The program goes from "On error.." directly to "dim frm.." and then to "con open"
Any idees?

VB

On Error GoTo WriteError  

      If My.Settings.IsFirstRun Then
            Dim frm As New frmActivation
            frm.ShowDialog()
            My.Settings.IsFirstRun = False
        Else
            Dim sm As New SecurityManager
            If sm.CheckKey(frmActivation.PasswordDecrypt(tActivationKey, 
                              tEncryptionKey)) Then
            Else
                Dim frm As New frmActivation
                frm.ShowDialog()
            End If
        End If

       con.Open()
       ..

What I have tried:

I have tried removing the error handler.

Posted 5-Jun-19 3:11am

Member 14131979

Updated 22-Jan-20 6:40am

RickZeeland

v2

Add a Solution

Comments

RickZeeland 5-Jun-19 9:25am

Are you sure you have the settings defined in your project - Settings tab page ?

Member 14131979 5-Jun-19 9:35am

Yes. Double checked it. Deleted it and dit it again.

Richard MacCutchan 5-Jun-19 9:44am

Step through the code with the debugger so you can see the actual values of all variables that are referred to in your if statements.

Dave Kreskowiak 5-Jun-19 11:30am

It's not skipping lines of code. It may look like it, but it's not.

And why on earth are you using "On Error Goto" is a VB.NET app? That's an old VB6 way or doing things that is there only for backwards compatibility of imported code. It shouldn't be used in new development.

The debugger is going to show you that it is NOT skipping lines of code. It's going to show you that you're not understanding what the code is doing. The debugger is there to debug YOU and show you what's really going on.

CPallini 5-Jun-19 12:00pm

You used the On Error GoTo statement. Such statememt skips lines of code whenever an erro occurs. The WriteError, to honour its own name, should give you relevant info about the error.

cigwork 30-Jun-19 16:27pm

> If sm.CheckKey(frmActivation.PasswordDecrypt(tActivationKey, tEncryptionKey))

On the basis of the fragment shown on any run after FirstRun frmActivation will be null (nothing) when the line above is executed. Given this I'd expect a null reference exception to be thrown. That plus the prehistoric on error goto handling is likely to give interesting results.

If the code is genuinely going from the attempt to open the activation dialog on first ever run to connection open then that suggests the activation form is being closed without any user interaction, so an error condition in frmActivation, perhaps an exception being swallowed, resulting in the form closing before it has a chance to display anything.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Doug- VisualBasic VB.NET · Answer 1 · 2020-01-22T06:41:00

I would use a try Catch end catch instead of the on Error. However the on error is not the issue since it is executing the con.open and the writeerror is not prior to that.

I would suggest looking at the VALUE of IsFirstRun in your settings. When the program starts is it "TRUE" ? If you change it during your run, do you set it back prior to exit? Is it of a Boolean type? If not you will have to do a direct comparison to the value in the settings.

If a string then If My.Settings.IsFirstRun = "True" Then
If a Integer then If My.Settings.IsFirstRun = 1 Then

I would suggest in the form_load event that you test with a msgbox(My.Settings.IsFirstRun.tostring) Or a debug.print(My.Settings.IsFirstRun.tostring) and see what you are working with.

You could also place one of those in front of you if statement to see what you have so you will know the expected outcome.

debug.print(My.Settings.IsFirstRun.tostring)
If My.Settings.IsFirstRun then