R
Robert T
We have a database that tracks instructors, courses, class schedules and
attendance. It started out as one .mdb and then I split it into a front and
back end. The back end resides on the Network server while the team members
[5] access the front end via their local “C†drive. Everyone uses a shared
password on the front end.
Everything works well, but obviously anyone can open the back end and look
at or modify data without a password. I’m sure you Access veterans can
recommend a way to place a minimum level of security on the back end. Can we
simply make the password for the back end the same as the front end?
I know these are elementary questions for Access veterans but I’m not one of
them, so I would appreciate your help and advice. Let me repeat, there is no
critical data such as account numbers of personal information that requires a
higher level of security. We just want to keep unauthorized people out of the
database.
Thanks,
Robert
attendance. It started out as one .mdb and then I split it into a front and
back end. The back end resides on the Network server while the team members
[5] access the front end via their local “C†drive. Everyone uses a shared
password on the front end.
Everything works well, but obviously anyone can open the back end and look
at or modify data without a password. I’m sure you Access veterans can
recommend a way to place a minimum level of security on the back end. Can we
simply make the password for the back end the same as the front end?
I know these are elementary questions for Access veterans but I’m not one of
them, so I would appreciate your help and advice. Let me repeat, there is no
critical data such as account numbers of personal information that requires a
higher level of security. We just want to keep unauthorized people out of the
database.
Thanks,
Robert