User System


DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 4 of 4

Thread: User System

  1. #1
    Ryan Nichols Guest

    User System


    Does anyone have some suggestions/ideas on creating a user tracking system
    for a program? i.e if they do something in a database, i can write the user
    name to the database ..

    Thanks


  2. #2
    Chris Smith Guest

    Re: User System

    What I have done in the past is force the user to log in, or grab the login
    name from the system. When the sub routine to access the database is called
    (or in your case the routine to save data) simply write the login/username
    information to a field in the database. By adding a simple security
    routine, you can even give levels of access (ie read only, read/write) to
    different users.

    "Ryan Nichols" <nichols@telxcom.com> wrote in message
    news:39c2c846$1@news.devx.com...
    >
    > Does anyone have some suggestions/ideas on creating a user tracking system
    > for a program? i.e if they do something in a database, i can write the

    user
    > name to the database ..
    >
    > Thanks
    >




  3. #3
    Dave Keighan Guest

    Re: User System

    Ryan

    In addition to what Chris has mentioned I have put additional fields in the
    tables where I need to know "who did what and when". I add two fields to any
    table where I need record level tracking. They are: "LastEdit" - used to
    store the Date/Time of the last edit and "UserRef" - which store the
    reference number (from the Users table Chris explained) of the person doing
    the edit. This will get you down to record level tracking. There are a
    number of ways to skin this cat, you may see more added soon.

    Dave


    "Chris Smith" <chris.smith@NOSPAMzymark.com> wrote in message
    news:39c391b3@news.devx.com...
    > What I have done in the past is force the user to log in, or grab the

    login
    > name from the system. When the sub routine to access the database is

    called
    > (or in your case the routine to save data) simply write the login/username
    > information to a field in the database. By adding a simple security
    > routine, you can even give levels of access (ie read only, read/write) to
    > different users.
    >
    > "Ryan Nichols" <nichols@telxcom.com> wrote in message
    > news:39c2c846$1@news.devx.com...
    > >
    > > Does anyone have some suggestions/ideas on creating a user tracking

    system
    > > for a program? i.e if they do something in a database, i can write the

    > user
    > > name to the database ..
    > >
    > > Thanks
    > >

    >
    >




  4. #4
    Darel_C Guest

    Re: User System


    Hi Guys,
    Normalize you databse.
    Instead of adding fields to the table edited,
    create a separate table with the primary key from the
    source table as the first field, editors name, date...
    This way you have a trail of all the changes, not just
    the last one. You could even capture each field that was
    changed along with the original value... Have the user
    even enter a reason for the change! Check out persisted
    recordsets and conflict resolution in MTS n-tier docs.

    "Dave Keighan" <codehog@hotmail.com> wrote:
    >Ryan
    >
    >In addition to what Chris has mentioned I have put additional fields in

    the
    >tables where I need to know "who did what and when". I add two fields to

    any
    >table where I need record level tracking. They are: "LastEdit" - used to
    >store the Date/Time of the last edit and "UserRef" - which store the
    >reference number (from the Users table Chris explained) of the person doing
    >the edit. This will get you down to record level tracking. There are a
    >number of ways to skin this cat, you may see more added soon.
    >
    >Dave
    >
    >
    >"Chris Smith" <chris.smith@NOSPAMzymark.com> wrote in message
    >news:39c391b3@news.devx.com...
    >> What I have done in the past is force the user to log in, or grab the

    >login
    >> name from the system. When the sub routine to access the database is

    >called
    >> (or in your case the routine to save data) simply write the login/username
    >> information to a field in the database. By adding a simple security
    >> routine, you can even give levels of access (ie read only, read/write)

    to
    >> different users.
    >>
    >> "Ryan Nichols" <nichols@telxcom.com> wrote in message
    >> news:39c2c846$1@news.devx.com...
    >> >
    >> > Does anyone have some suggestions/ideas on creating a user tracking

    >system
    >> > for a program? i.e if they do something in a database, i can write the

    >> user
    >> > name to the database ..
    >> >
    >> > Thanks
    >> >

    >>
    >>

    >
    >



Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center