Security for an Audit Log table

[Pack10]

My management wants me to "lock down" our audit log table.
I have an Access 2007 accdb file. By lock down, they don't want
anyone other than myself to be able to access the table other
than the app writing to it or reading from it.
I know I can hide it, and lock out the F11 using the shift key, is there anything else I can do?

 

[MazeWorX]

compile the file .accde format

HTH << MaZeWorX >> "I have not failed I have only found ten thousand ways that don't work" <<Edison>>

 

[MazeWorX]

Sorry should of added you cant make design changes once its done so be sure to backup your design master

HTH << MaZeWorX >> "I have not failed I have only found ten thousand ways that don't work" <<Edison>>

 

[Pack10]

My application is split. How can I stop someone from getting into the back end? THe compile will stop them from getting to the data from the front end, correct?

 

[MazeWorX]

compile the backend after you hide the tables and disable the bypass keys

HTH << MaZeWorX >> "I have not failed I have only found ten thousand ways that don't work" <<Edison>>

 

[MazeWorX]

Sorry again: you can also PW protect the db but then you will need to pass the password when writing to the table

HTH << MaZeWorX >> "I have not failed I have only found ten thousand ways that don't work" <<Edison>>

 

[Pack10]

OK, forgive me, but I can compile the back-end? What about the front-end.

 

[MazeWorX]

simple answer is you can make any db front or back ends into an accde file format. remember to hide the tables or you can still link to them. compiling it will stop users from undoing your database properties

HTH << MaZeWorX >> "I have not failed I have only found ten thousand ways that don't work" <<Edison>>

 

[Pack10]

If the front and back end are compiled, can someone get into the tables? As for password protecting, will Access ask for the password each time it writes to the table, if so that won't work here. The users would kill me.

 

[Pack10]

If I compile the back end and disable the shift key, how will I get into the back end to do research or maintenance. And doesn't everything have to be re-linked again?

 

[MazeWorX]

relinked no

if you have established your links prior to securing the BE.

think of it this way you create an Admin db to retrieve the data that has established links. Keep a working copy of the BE so you can make db object changes. When needed you can import the data into your new BE and re write the BE db to the server location. Establish the links now and the ability to retrieve the data

When pass wording a BE the pw needs to be passed in your code when you establish the connection. in short you would need to recode the db to handle a password.

If you make the tables hidden then compile the db they cant see the tables to connect to them.

HTH << MaZeWorX >> "I have not failed I have only found ten thousand ways that don't work" <<Edison>>