Results 1 to 3 of 3
  1. #1
    Join Date
    Oct 2015
    Posts
    3

    Question Unanswered: Add identifying Information for User actions that took place.

    I don't know if this can be done. I'm using Access 2010 and I have users updating information on a hourly basis.

    Can I have a field that basically shows the last user that edited the form or saved it?

  2. #2
    Join Date
    Nov 2004
    Location
    out on a limb
    Posts
    13,692
    Provided Answers: 59
    There various options
    The CURRENTUSER function, returns the current Access user
    The ENVIRON function
    The windows API call documented by Dev Ashish that returns the Network lohon of the current user.

    Of the 3 my preference is for the API call. Why?
    Currentuser returns the userid the person logged onto this instance of Access. Its not especially secure or reliable.
    ENVIRON should be the same as the API call, ie the windows userid of the person, however ive seen it spoofed so I dobt trust it.
    The API call has the advantage that coupled with good network policies (one id per user, only one current logon per user and so on) you have a mechanism which can uniquely identify a user. Dev Ashish has also documented hiw to get the computername as well. If tied down with good network user policies the infomation can be good enough for legal requirements.

    Have a look at the audit trail by Allen Browne and others. An aydit trail is probably over the top for what you are looking at but its probably worth reading none the less
    I'd rather be riding on the Tiger 800 or the Norton

  3. #3
    Join Date
    Oct 2015
    Posts
    3
    Quote Originally Posted by healdem View Post
    There various options
    The CURRENTUSER function, returns the current Access user
    The ENVIRON function
    The windows API call documented by Dev Ashish that returns the Network lohon of the current user.

    Of the 3 my preference is for the API call. Why?
    Currentuser returns the userid the person logged onto this instance of Access. Its not especially secure or reliable.
    ENVIRON should be the same as the API call, ie the windows userid of the person, however ive seen it spoofed so I dobt trust it.
    The API call has the advantage that coupled with good network policies (one id per user, only one current logon per user and so on) you have a mechanism which can uniquely identify a user. Dev Ashish has also documented hiw to get the computername as well. If tied down with good network user policies the infomation can be good enough for legal requirements.

    Have a look at the audit trail by Allen Browne and others. An aydit trail is probably over the top for what you are looking at but its probably worth reading none the less

    Ok ill have a look. Hopefully i come back alive

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •