Permissions Database

[AccessNewbie]

I replaced an access genius and I'm taking classes to learn access. But,
currently I am having problems understand and using a permissions database
that was set up previously. I have six access .mde programs that use the
same .mdb file for permissions. the permissions are set up by ntlogin id,
then by dept code, then by a number (1-4) - the number sets the permssions by
how much they can edit, add or delete, the dept code only allows the user
access to information in thier dept, the ntlogin is automatic from the
initial login into the network and there is no separate or additional login
after that. The permissions mdb has
two tables and between these two tables all six mdb programs get their
permissions. I hope this is understandable. What I'm trying to find out is
how are these permissions set and how is the ntlogin used (from the initial
login into the network vs a separsate login into access). The ntlogin id is
also used in reports. Also, the original mdb files for the six mde programs
have been coded and there is no legible way for me to understand any of this
code. I will be making new programs and would like to use these same
permissions.
thanks for any and all help.

 

[Mr B]

I am not trying to ignore your quertions, but I have a couple of questions
before I would want to try to answer your questions.

Do you have the original mdb files for each of your six mde files? In order
to see exactly how each of the department values and the permissions are
being used you will certainly need to take a look at the VBA code that was
written by the other developer.

If you do not have the original mdb files you may be forced to determine
your best usage of the available info during your development process.

You do not indicate why a complete re-write is necessary.

 

[John W. Vinson]

I replaced an access genius and I'm taking classes to learn access.

Based on the nature of the problem you're having, I'd have to take issue with
the characterization of this person!

But, currently I am having problems understand and using a permissions database
that was set up previously.

That's one of the problems. Home-grown security systems tend to be much more
complicated than the (already complicated enough!) Access workgroup security,
and often are either more vulnerable to either hacking or to legitimate users
getting locked out - or both.

I have six access .mde programs that use the
same .mdb file for permissions. the permissions are set up by ntlogin id,
then by dept code, then by a number (1-4) - the number sets the permssions by
how much they can edit, add or delete, the dept code only allows the user
access to information in thier dept, the ntlogin is automatic from the
initial login into the network and there is no separate or additional login
after that. The permissions mdb has
two tables and between these two tables all six mdb programs get their
permissions. I hope this is understandable.

Not without seeing the code and - probably - spending a few hours' deciphering
what the devloper did.

What I'm trying to find out is
how are these permissions set and how is the ntlogin used (from the initial
login into the network vs a separsate login into access). The ntlogin id is
also used in reports. Also, the original mdb files for the six mde programs
have been coded and there is no legible way for me to understand any of this
code. I will be making new programs and would like to use these same
permissions.
thanks for any and all help.

If the original mdb programs are inaccessible or unreadable, then I suspect
that you're out of luck. I'd really suggest reading up on Workgroup security
and setting it up yourself. As I say, it's complicated; I'd print out the
document from the link below, *study it carefully*, get a good night's sleep,
and read it *again*, even more carefully! Then follow the steps to secure your
database.

How to remove the code that this developer put in... I don't know, and I wish
you luck.

Microsoft Access 2000 Security FAQ:

http://support.microsoft.com/kb/207793/en-us

John W. Vinson [MVP]