capturing user login and logout time using vb into sql server 2005 database

Question

1.00/5 (1 vote)

See more:

I need suggestions using vb6 on a way (code etc) of capturing users logintime, logoutime, log_ID into an sql server 2005 database. suggestions on structure of the table, etc. i.e audit trail on login & logout

Posted 17-Apr-13 3:53am

Aleu Philip

Updated 17-Apr-13 5:10am

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)

CHill60 · Answer 1 · 2013-04-17T06:00:00

Well as you are going to log to a database everytime someone logs onto your application then you could just use database triggers to capture that information (if you've applied SP2)
Have a look at https://www.simple-talk.com/sql/t-sql-programming/logon-triggers/[^]
and another sample at
http://blog.sqlauthority.com/2009/06/26/sql-server-interesting-observation-of-logon-trigger-on-all-servers-solution/[^]
and
http://msdn.microsoft.com/en-gb/library/bb326598(v=sql.90).aspx[^]

That may get messy if other applications can log on to the same database, but you could use the principle / table structure and write to it directly from your application.

A general observation - if this is new code (and not an enhancement to a large existing suite of applications) then you should really consider using more up-to-date technology than VB6 (which is largely out of support) - even if it is part of an existing suite you can still use .NET see http://www.microsoft.com/en-gb/download/details.aspx?id=3264[^]