Question Audittrail and securing a DB

[SOS]

As long as you have what you need and you know the limitations, that is good.

Glad we could help, even through all of the back and forth.

 

[irish634]

I never said that you can't figure out which pc it came from and when. You can't figure out WHO (the big WHO) did it. And that CAN be VERY important. Just knowing which computer and when it came in is not very informative if you do not keep detailed records as to who was using which computer when. So, you can disagree all you want but the fact of the matter is without secure INDIVIDUAL logins you CAN NOT prove who did what and therefore an audit trail is SEVERELY lacking.

My response was geared toward the lack of network logins. He can still create custom DB logins (not Access Security) and each employee logs into the db. Then you CAN figure out who did what. That was in response to your statement:

So they do not have individual network logins? If that is the case, you really are not going to be able to tie anything to anyone - at all. Seriously, you might as well scrap the audit as well. You can capture what was changed and when, and on what computer, but you cannot identify who did it.

No need to become defensive, and I still disagree with the above statements, the context of which informs the OP that it can't be done because there are no network logins. There is no need to scrap the use of anything because they don't use network logins. A custom db login can be created which will allow him to capture the WHO. Subsequent posts address this.

Have a nice day.

 

[SOS]

A custom db login can be created which will allow him to capture the WHO.

And that is as secure as tying your bike to a bike rack with a shoestring. They should know the limitations.

Have a nice day.