 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
MS Access Forum / Multiuser / Networking / May 2006Recording user events
Hi There I wonder if someone could help me please. I have a multi-user database application and I would like to record specific events within the database, especially the user that has initiated the event. At the moment I have a startup form that asks for the user to enter his/her name and it is this that I currently record against certain events. However this could be I'd like to go one stage further and record the name of the computer the event was initialised on and also the username the person used to log in to our network (Some people use Win 98 others use XP). Does anyone know of a way of doing this please. I'd be very grateful of any help you may be able to give. Many thanks David. > Hi There > [quoted text clipped - 13 lines] > > David. Search the help for "Environ". Although some developers frown upon it because it can apparently be changed at a command prompt, I find it useful, but then again most of my users wouldn't know a command prompt if it bit them on the leg. You'd have to do a risk assessment for your own situation. HTH - Keith. www.keithwilby.com >Search the help for "Environ". Although some developers frown upon it >because it can apparently be changed at a command prompt, I find it useful, >but then again most of my users wouldn't know a command prompt if it bit >them on the leg. You'd have to do a risk assessment for your own situation. I've done some more research. The risk appears to only happen if you open the command prompt, change the environment variable and then execute the msaccess.exe from that command prompt. A daunting task for 99.99% of the users Changing the environment variable in the command prompt does not affect other programs that you start from Windows. But only from that particular command prompt. However that 00.01% of the users that know about this could also be the malicious users who want to blame data problems on other people. Hmmm, being the sneaky bugger that I am I'd put a check in to compare the value of the environment variable against the API call. If different without an exceedingly good reason that'd be grounds to terminate the employee. Tony  SignatureTony Toews, Microsoft Access MVP Please respond only in the newsgroups so that others can read the entire thread of messages. Microsoft Access Links, Hints, Tips & Accounting Systems at http://www.granite.ab.ca/accsmstr.htm >Search the help for "Environ". Although some developers frown upon it >because it can apparently be changed at a command prompt, I find it useful, >but then again most of my users wouldn't know a command prompt if it bit >them on the leg. You'd have to do a risk assessment for your own situation. Oh yeah - API: Get Login name http://www.mvps.org/access/api/api0008.htm Tony SignatureTony Toews, Microsoft Access MVP Please respond only in the newsgroups so that others can read the entire thread of messages. Microsoft Access Links, Hints, Tips & Accounting Systems at http://www.granite.ab.ca/accsmstr.htm >>Search the help for "Environ". Although some developers frown upon it >>because it can apparently be changed at a command prompt, I find it [quoted text clipped - 5 lines] > Oh yeah - API: Get Login name > http://www.mvps.org/access/api/api0008.htm Cheers Tony. Keith. Thanks everyone for your help. I don't think people here would know a command prompt if it bit them on the leg either so I think i'm safe! David >>>Search the help for "Environ". Although some developers frown upon it >>>because it can apparently be changed at a command prompt, I find it [quoted text clipped - 9 lines] > > Keith. > Oh yeah - API: Get Login name > http://www.mvps.org/access/api/api0008.htm So, because you can get the user's network login name using the API, and it is reliable (as it has seemed to be for me), and works every time, why would you want/need to _also_ obtain the name from the ENVIRON which is, at least in some cases, unreliable? Larry I have users using the environment user variable as the Access login name. That is exceptionally easy to implement. I know that using environ inside a program is not the same as using it in the windows shell, but I think that at least to a limited extent the same criteria apply: it is easy to implement and understand. In any serious program development, that's worth something. (david) > > Oh yeah - API: Get Login name > > http://www.mvps.org/access/api/api0008.htm [quoted text clipped - 5 lines] > > Larry >So, because you can get the user's network login name using the API, and it >is reliable (as it has seemed to be for me), and works every time, why would >you want/need to _also_ obtain the name from the ENVIRON which is, at least >in some cases, unreliable? Why do both? Because I want to see if anyone is being a sneaky bugger. If it's different then maybe that person is trying to masquerade as someone else. And I want to know that. Tony SignatureTony Toews, Microsoft Access MVP Please respond only in the newsgroups so that others can read the entire thread of messages. Microsoft Access Links, Hints, Tips & Accounting Systems at http://www.granite.ab.ca/accsmstr.htm |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.