Question : Security with MS Access

Hi experts, I have 2 mde & 2 mdb files which are to reside on the server. The 2 mde files (A.mde & B.mde) are the front end programs used for data entry that links & updates data to the 2 mdb files (C.mdb & D.mdb). C & D.mdb acts as databases that contains only tables with sensitive data. A.mde only links to C.mdb whereas B.mde links to both C.mdb & D.mdb.

Now the difficult part is, users are allowed to open & update records thru A.mde & B.mde but they are not allowed to delete/rename the physical files. As for the databases, users are not allowed to even open the file for viewing. They are not allowed to delete/rename the files too.

I have tried using NT security to block the databases with "No Access" but by doing that, users will not be able to update records thru the mde programs.

Can anyone suggest any alternatives in securing the databases but still enable users to add & update records to the databases using the programs? I'm using purely access in 97 version.

Thanx, Lelyn

Answer : Security with MS Access

2. OK, my standard is: Administrator doesn't change, users do. BUT all you do is change the date of last password change in the sysUser table (for the user you want to never change) to a date a long way in the future, e.g. see my example in the db (sending tonight).

3. No, seems OK.

1. Yes, that's right. The workgroup manager application is normally set to system.mdw, i.e. it always logs users in with system.mdw - It's just that they never see it. It is only the last joined workgroup (i.e. current) that is important.