enhance...rotate, now uncrop!!
January 2, 2010 11:38 AM
[CSIfilter] Need to find out who has modified certain records in Office Access.
[CSIfilter] Need to find out who has modified certain records in Office Access. My google-fu only found me how to add timestamps when users modify records. Is this possible?
[CSIfilter] Need to find out who has modified certain records in Office Access. My google-fu only found me how to add timestamps when users modify records. Is this possible?
See: http://office.microsoft.com/en-us/access/HA010345351033.aspx
Among other links: http://www.google.com/#hl=en&source=hp&q=time+stamp+ms+access&aq=f&aqi=g-sx1&oq=&fp=cbc2f75bf9d43a8f
If you want to do this retrospectively, I'm pretty sure that can't be done.
posted by dfriedman at 11:46 AM on January 2, 2010
Among other links: http://www.google.com/#hl=en&source=hp&q=time+stamp+ms+access&aq=f&aqi=g-sx1&oq=&fp=cbc2f75bf9d43a8f
If you want to do this retrospectively, I'm pretty sure that can't be done.
posted by dfriedman at 11:46 AM on January 2, 2010
The timestamp was the only thing I could found on google, which doesn't really really help. I need to find out if a certain user modified several records for his own benefits or not.
So, retrospectively.
If that's not possible, is there a way to do it prospectively?
posted by jstarlee at 11:50 AM on January 2, 2010
So, retrospectively.
If that's not possible, is there a way to do it prospectively?
posted by jstarlee at 11:50 AM on January 2, 2010
It depends on where the database is stored. If it's local(on his machine), the timestamps + a frequent backup would allow you to see when the original was entered, then crossreference the changes and when they were made.
If it's on a server, you'll have more options. You'll probably need to do this as a one-two punch kind of thing. One, get the timestamp feature up, and then get a second program, something like an extensive logging program, running on the server, that will tell you who's connected, and what files are open. There are a few out there, but I haven't had to deal with Access in a while. Then cross reference with the timestamp, and you've got your proof.
Or, you could install a keylogging program or the suspected employees computer. It's a pain, but you'll have a secret way of finding out exactly what he's entering and doing.
posted by chambers at 12:12 PM on January 2, 2010
If it's on a server, you'll have more options. You'll probably need to do this as a one-two punch kind of thing. One, get the timestamp feature up, and then get a second program, something like an extensive logging program, running on the server, that will tell you who's connected, and what files are open. There are a few out there, but I haven't had to deal with Access in a while. Then cross reference with the timestamp, and you've got your proof.
Or, you could install a keylogging program or the suspected employees computer. It's a pain, but you'll have a secret way of finding out exactly what he's entering and doing.
posted by chambers at 12:12 PM on January 2, 2010
Unless you've enabled filesystem auditing on the server prior, or enabled some sort of logging functionality in MS Access itself, I don't think you can do this.
For future reference, you can enable filesystem auditing in the Windows server OS itself, and then every access to specified files can be logged.
posted by me & my monkey at 12:24 PM on January 2, 2010
For future reference, you can enable filesystem auditing in the Windows server OS itself, and then every access to specified files can be logged.
posted by me & my monkey at 12:24 PM on January 2, 2010
From my experience you won't get the granularity you need just from filesystem auditing for Access and AFAIK internally it will not track access/modifications unless someone designed and programmed that into your custom Access solution/application.
posted by jkaczor at 12:38 PM on January 2, 2010
posted by jkaczor at 12:38 PM on January 2, 2010
« Older Can I put my terracotta casserole dish on an... | Help me cope with mitering my baseboards. Newer »
This thread is closed to new comments.
posted by shothotbot at 11:41 AM on January 2, 2010