How to create a login history in VB.NET and saves it into mysql workbench database?

Question

0.00/5 (No votes)

See more:

I only know few knowledge about vb.net and I am trying to understand it as much as I can. I've tried the code below for login button to save the login date, and it works. Yet, I'm not sure what code to input for logout button. Please help me about this, thankyou! :)

What I have tried:

Private Sub Button1_Click(sender As Object, e As EventArgs) Handles Button1.Click

      Dim command As New MySqlCommand("SELECT `StudentId`, `Account Password` FROM `usersaccount` WHERE `StudentId` = @username AND `Account Password` = @password", connection)

      command.Parameters.Add("@username", MySqlDbType.VarChar).Value = Username.Text
      command.Parameters.Add("@password", MySqlDbType.VarChar).Value = Pass.Text

      Dim adapter As New MySqlDataAdapter(command)
      Dim table As New DataTable()

      adapter.Fill(table)

      If table.Rows.Count = 0 Then

          MessageBox.Show("Invalid Username Or Password")

      Else

          Using con As New MySqlConnection("server=localhost;username=root;password=;database=logrecord"),
                  cmd As New MySqlCommand("Insert into logrecord (Username, Date, Login) Values(@Username, @Date, @Login);", con)

              cmd.Parameters.Add("@Username", MySqlDbType.VarChar).Value = Username.Text
              cmd.Parameters.Add("@Date", MySqlDbType.VarChar).Value = Date.Now.ToString("dd/MM/yyyy")
              cmd.Parameters.Add("@Login", MySqlDbType.VarChar).Value = TimeOfDay.ToString("hh:mm:ss")
              con.Open()
              cmd.ExecuteNonQuery()
          End Using
          Form3.Show()
          Me.Hide()


      End If

  End Sub

Posted 1-Nov-21 3:51am

Myln29

Updated 4-Nov-21 3:41am

v2

Add a Solution

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)

OriginalGriff · Answer 1 · 2021-11-01T04:51:00

Never store passwords in clear text - it is a major security risk. There is some information on how to do it here: Password Storage: How to do it.[^]

And remember: if this is web based and you have any European Union users then GDPR applies and that means you need to handle passwords as sensitive data and store them in a safe and secure manner. Text is neither of those and the fines can be .... um ... outstanding. In December 2018 a German company received a relatively low fine of €20,000 for just that.

For alogout, you will have to change you DB to add a "activity type" code to your table: perhaps 0 for Login, 1 for Logout, with other values reserved for later log events.
Then you just add the activity code to your login code above, and duplicate that code with the Logout activity code for logout.

I'd also change the two columns Date and Login to a single column "Timestamp" and make it DateTime instead - storing everything as a string may seem like a simple solution, but when you want to use them it becomes a PITA: string comparisons are done character by character with the result being entirely on the first difference found. So the string dates "02/01/2001" and "01/12/2021" will compare badly, with the later date coming first!
Using DATETIME columns makes that a whole lot easier as it can compare them directly.