Click here to Skip to main content
14,297,835 members
Rate this:
Please Sign up or sign in to vote.
See more:
I found it best to change from string a date variables for checking for duplicates to just checking row by row using the information that was in the datarow.

However, I tried to convert my class variables to a just the datarow source.

here is the original code:

If newindividual.First_name = matchedfirstname And newindividual.Last_name = matchedlastname _
           And newindividual.Date_of_birth = matchedDOB Then
            matched = True
            GoTo found
        ElseIf newindividual.First_name = matchedfirstname And newindividual.Last_name = matchedlastname _
               And newindividual.Date_of_death = matchedDOD And newindividual.Date_of_birth = matchedDOB Then
            matched = True
            GoTo found
        ElseIf newindividual.First_name = matchedfirstname And newindividual.Last_name = matchedlastname _
               And newindividual.Date_of_death = matchedDOD Then
            matched = True
            GoTo found
        End If


Here is what I tried to change the information into

If StrConv(Trim(temptable.Rows(I)("First_name").ToString), vbProperCase) = StrConv(Trim(dt.Rows(I2)("First_name").ToString), vbProperCase) And StrConv(Trim(temptable.Rows(I)("Last_name").ToString), vbProperCase) = StrConv(Trim(dt.Rows(I2)("Last_name").ToString), vbProperCase) Then
           If temptable.Columns.Contains("Date_of_birth") And Not IsDBNull(temptable.Rows(I)("Date_of_birth")) And temptable.Columns.Contains("Date_of_death") And Not IsDBNull(temptable.Rows(I)("Date_of_death")) Then
               If Not IsDBNull(dt.Rows(I2)("Date_of_birth")) And Not IsDBNull(dt.Rows(I2)("Date_of_death")) Then
                   If CDate(Trim(temptable.Rows(I)("Date_of_birth").ToString)) = CDate(Trim(dt.Rows(I2)("Date_of_birth").ToString)) And CDate(Trim(temptable.Rows(I)("Date_of_death").ToString)) = CDate(Trim(dt.Rows(I2)("Date_of_death"))) Then
                       matched = True
                       GoTo found
                   End If
               End If
           ElseIf temptable.Columns.Contains("Date_of_birth") And Not IsDBNull(temptable.Rows(I)("Date_of_birth")) Then
               If Not IsDBNull(dt.Rows(I2)("Date_of_birth")) Then
                   If CDate(Trim(temptable.Rows(I)("Date_of_birth").ToString)) = CDate(Trim(dt.Rows(I2)("Date_of_birth").ToString)) Then
                       matched = True
                       GoTo found
                   End If
               End If
           ElseIf temptable.Columns.Contains("Date_of_death") And Not IsDBNull(temptable.Rows(I)("Date_of_death")) Then
               If Not IsDBNull(dt.Rows(I2)("Date_of_death")) Then
                   If CDate(Trim(temptable.Rows(I)("Date_of_death").ToString)) = CDate(Trim(dt.Rows(I2)("Date_of_death").ToString)) Then
                       matched = True
                       GoTo found
                   End If
               End If
           End If
       End If


When I run the new code in a nested loop there are more iterations in loop 2, However, the original code has the correct amount of iterations. Should the not be the same?

What I have tried:

I have tried to change the if statements around to see if the out come would be different.
Posted
Updated 21-Jun-19 19:14pm

1 solution

Rate this:
Please Sign up or sign in to vote.

Solution 1

Compiling does not mean your code is right! :laugh:
Think of the development process as writing an email: compiling successfully means that you wrote the email in the right language - English, rather than German for example - not that the email contained the message you wanted to send.

So now you enter the second stage of development (in reality it's the fourth or fifth, but you'll come to the earlier stages later): Testing and Debugging.

Start by looking at what it does do, and how that differs from what you wanted. This is important, because it give you information as to why it's doing it. For example, if a program is intended to let the user enter a number and it doubles it and prints the answer, then if the input / output was like this:
Input   Expected output    Actual output
  1            2                 1
  2            4                 4
  3            6                 9
  4            8                16
Then it's fairly obvious that the problem is with the bit which doubles it - it's not adding itself to itself, or multiplying it by 2, it's multiplying it by itself and returning the square of the input.
So with that, you can look at the code and it's obvious that it's somewhere here:
Private Function Double(ByVal value As Integer) As Integer
    Return value * value
End Function

Once you have an idea what might be going wrong, start using the debugger to find out why. Put a breakpoint on the first line of the method, and run your app. When it reaches the breakpoint, the debugger will stop, and hand control over to you. You can now run your code line-by-line (called "single stepping") and look at (or even change) variable contents as necessary (heck, you can even change the code and try again if you need to).
Think about what each line in the code should do before you execute it, and compare that to what it actually did when you use the "Step over" button to execute each line in turn. Did it do what you expect? If so, move on to the next line.
If not, why not? How does it differ?
Hopefully, that should help you locate which part of that code has a problem, and what the problem is.
This is a skill, and it's one which is well worth developing as it helps you in the real world as well as in development. And like all skills, it only improves by use!
   

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




CodeProject, 503-250 Ferrand Drive Toronto Ontario, M3C 3G8 Canada +1 416-849-8900 x 100