Welcome to SPN

Register and Join the most happening forum of Sikh community & intellectuals from around the world.

Sign Up Now!

General Access Question

Discussion in 'Information Technology' started by mattymatt79, Nov 2, 2005.

  1. mattymatt79

    mattymatt79
    Expand Collapse
    Guest

    ok,
    well I have a pretty decent grasp on how access works, and what i want to do.
    I have the database pretty much done and the forms completed I just have one
    last thing to accomplish and i dont know how to really finish it up.

    Ill explain the situation.
    I have a database that tracks people and contacting them.

    Is there a way to lock down who can access what with Active Directory based
    on thier login?

    Also, searching, as in say a manager can search all aspects of information
    on the database, but the person who entered it can only access thier
    information?

    Also can it be that the person who entered it can not delete it, but the
    manager can manipulate all the data?

    I have the table done, just not the search aspect of it.

    Also if there was a way to just put in everyone that was accessing the
    database could then instead lock down what search aspects were involved with
    the database then?
     
  2. Loading...


  3. Douglas J Steele

    Douglas J Steele
    Expand Collapse
    Guest

    You can use Access User Level Security to achieve most of what you're
    looking for, but Access doesn't interact with Active Directory: you'll have
    to create new user ids within Access, and the users will have to maintain
    separate passwords for those new ids.

    --
    Doug Steele, Microsoft Access MVP
    http://I.Am/DougSteele
    (no e-mails, please!)


    "mattymatt79" <mattymatt79@discussions.microsoft.com> wrote in message
    news:E013C795-6872-40C6-B27C-F1018A5D439E@microsoft.com...
    > ok,
    > well I have a pretty decent grasp on how access works, and what i want to

    do.
    > I have the database pretty much done and the forms completed I just have

    one
    > last thing to accomplish and i dont know how to really finish it up.
    >
    > Ill explain the situation.
    > I have a database that tracks people and contacting them.
    >
    > Is there a way to lock down who can access what with Active Directory

    based
    > on thier login?
    >
    > Also, searching, as in say a manager can search all aspects of information
    > on the database, but the person who entered it can only access thier
    > information?
    >
    > Also can it be that the person who entered it can not delete it, but the
    > manager can manipulate all the data?
    >
    > I have the table done, just not the search aspect of it.
    >
    > Also if there was a way to just put in everyone that was accessing the
    > database could then instead lock down what search aspects were involved

    with
    > the database then?
     
  4. mattymatt79

    mattymatt79
    Expand Collapse
    Guest

    Ok great post and thank you, but I'm still not sure if using the access users
    and groups would do exactly what I want them to do.

    Example
    User A (general user) enters in customer information
    User B (general user) enters in customer information

    Wouldn't even with security since they are the exact table go to the exact
    same security setting? Meaning that user A could view user B's information?

    Also User C (manager) needs to be able to view all info, which is simple, I
    just make a new group for them, but what about User A and B?


    "Douglas J Steele" wrote:

    > You can use Access User Level Security to achieve most of what you're
    > looking for, but Access doesn't interact with Active Directory: you'll have
    > to create new user ids within Access, and the users will have to maintain
    > separate passwords for those new ids.
    >
    > --
    > Doug Steele, Microsoft Access MVP
    > http://I.Am/DougSteele
    > (no e-mails, please!)
    >
    >
    > "mattymatt79" <mattymatt79@discussions.microsoft.com> wrote in message
    > news:E013C795-6872-40C6-B27C-F1018A5D439E@microsoft.com...
    > > ok,
    > > well I have a pretty decent grasp on how access works, and what i want to

    > do.
    > > I have the database pretty much done and the forms completed I just have

    > one
    > > last thing to accomplish and i dont know how to really finish it up.
    > >
    > > Ill explain the situation.
    > > I have a database that tracks people and contacting them.
    > >
    > > Is there a way to lock down who can access what with Active Directory

    > based
    > > on thier login?
    > >
    > > Also, searching, as in say a manager can search all aspects of information
    > > on the database, but the person who entered it can only access thier
    > > information?
    > >
    > > Also can it be that the person who entered it can not delete it, but the
    > > manager can manipulate all the data?
    > >
    > > I have the table done, just not the search aspect of it.
    > >
    > > Also if there was a way to just put in everyone that was accessing the
    > > database could then instead lock down what search aspects were involved

    > with
    > > the database then?

    >
    >
    >
     
  5. Douglas J. Steele

    Douglas J. Steele
    Expand Collapse
    Guest

    You'd have to use a query to let them get at the data, as opposed to using
    the table directly.

    --
    Doug Steele, Microsoft Access MVP
    http://I.Am/DougSteele
    (no e-mails, please!)



    "mattymatt79" <mattymatt79@discussions.microsoft.com> wrote in message
    news:635B5792-4700-450A-9544-A34ED79838FA@microsoft.com...
    > Ok great post and thank you, but I'm still not sure if using the access
    > users
    > and groups would do exactly what I want them to do.
    >
    > Example
    > User A (general user) enters in customer information
    > User B (general user) enters in customer information
    >
    > Wouldn't even with security since they are the exact table go to the exact
    > same security setting? Meaning that user A could view user B's
    > information?
    >
    > Also User C (manager) needs to be able to view all info, which is simple,
    > I
    > just make a new group for them, but what about User A and B?
    >
    >
    > "Douglas J Steele" wrote:
    >
    >> You can use Access User Level Security to achieve most of what you're
    >> looking for, but Access doesn't interact with Active Directory: you'll
    >> have
    >> to create new user ids within Access, and the users will have to maintain
    >> separate passwords for those new ids.
    >>
    >> --
    >> Doug Steele, Microsoft Access MVP
    >> http://I.Am/DougSteele
    >> (no e-mails, please!)
    >>
    >>
    >> "mattymatt79" <mattymatt79@discussions.microsoft.com> wrote in message
    >> news:E013C795-6872-40C6-B27C-F1018A5D439E@microsoft.com...
    >> > ok,
    >> > well I have a pretty decent grasp on how access works, and what i want
    >> > to

    >> do.
    >> > I have the database pretty much done and the forms completed I just
    >> > have

    >> one
    >> > last thing to accomplish and i dont know how to really finish it up.
    >> >
    >> > Ill explain the situation.
    >> > I have a database that tracks people and contacting them.
    >> >
    >> > Is there a way to lock down who can access what with Active Directory

    >> based
    >> > on thier login?
    >> >
    >> > Also, searching, as in say a manager can search all aspects of
    >> > information
    >> > on the database, but the person who entered it can only access thier
    >> > information?
    >> >
    >> > Also can it be that the person who entered it can not delete it, but
    >> > the
    >> > manager can manipulate all the data?
    >> >
    >> > I have the table done, just not the search aspect of it.
    >> >
    >> > Also if there was a way to just put in everyone that was accessing the
    >> > database could then instead lock down what search aspects were involved

    >> with
    >> > the database then?

    >>
    >>
    >>
     
  6. mattymatt79

    mattymatt79
    Expand Collapse
    Guest

    Ok, that makes perfect sense, but would I then have to create a seperate
    query for everyone that would be accessing the data inside the database? Or
    is there a way to automate this?

    Again, thanks for the response all

    "Douglas J. Steele" wrote:

    > You'd have to use a query to let them get at the data, as opposed to using
    > the table directly.
    >
    > --
    > Doug Steele, Microsoft Access MVP
    > http://I.Am/DougSteele
    > (no e-mails, please!)
    >
    >
    >
    > "mattymatt79" <mattymatt79@discussions.microsoft.com> wrote in message
    > news:635B5792-4700-450A-9544-A34ED79838FA@microsoft.com...
    > > Ok great post and thank you, but I'm still not sure if using the access
    > > users
    > > and groups would do exactly what I want them to do.
    > >
    > > Example
    > > User A (general user) enters in customer information
    > > User B (general user) enters in customer information
    > >
    > > Wouldn't even with security since they are the exact table go to the exact
    > > same security setting? Meaning that user A could view user B's
    > > information?
    > >
    > > Also User C (manager) needs to be able to view all info, which is simple,
    > > I
    > > just make a new group for them, but what about User A and B?
    > >
    > >
    > > "Douglas J Steele" wrote:
    > >
    > >> You can use Access User Level Security to achieve most of what you're
    > >> looking for, but Access doesn't interact with Active Directory: you'll
    > >> have
    > >> to create new user ids within Access, and the users will have to maintain
    > >> separate passwords for those new ids.
    > >>
    > >> --
    > >> Doug Steele, Microsoft Access MVP
    > >> http://I.Am/DougSteele
    > >> (no e-mails, please!)
    > >>
    > >>
    > >> "mattymatt79" <mattymatt79@discussions.microsoft.com> wrote in message
    > >> news:E013C795-6872-40C6-B27C-F1018A5D439E@microsoft.com...
    > >> > ok,
    > >> > well I have a pretty decent grasp on how access works, and what i want
    > >> > to
    > >> do.
    > >> > I have the database pretty much done and the forms completed I just
    > >> > have
    > >> one
    > >> > last thing to accomplish and i dont know how to really finish it up.
    > >> >
    > >> > Ill explain the situation.
    > >> > I have a database that tracks people and contacting them.
    > >> >
    > >> > Is there a way to lock down who can access what with Active Directory
    > >> based
    > >> > on thier login?
    > >> >
    > >> > Also, searching, as in say a manager can search all aspects of
    > >> > information
    > >> > on the database, but the person who entered it can only access thier
    > >> > information?
    > >> >
    > >> > Also can it be that the person who entered it can not delete it, but
    > >> > the
    > >> > manager can manipulate all the data?
    > >> >
    > >> > I have the table done, just not the search aspect of it.
    > >> >
    > >> > Also if there was a way to just put in everyone that was accessing the
    > >> > database could then instead lock down what search aspects were involved
    > >> with
    > >> > the database then?
    > >>
    > >>
    > >>

    >
    >
    >
     
  7. Douglas J Steele

    Douglas J Steele
    Expand Collapse
    Guest

    You should be able to create a query that picks up their Access User Id
    (using the CurrentUser function), and only returns the records for that Id,
    unless they're in a group that should give them access to all the records.

    --
    Doug Steele, Microsoft Access MVP
    http://I.Am/DougSteele
    (no e-mails, please!)


    "mattymatt79" <mattymatt79@discussions.microsoft.com> wrote in message
    news:30A64DA4-1B5B-4C2A-B5B7-F7441424F601@microsoft.com...
    > Ok, that makes perfect sense, but would I then have to create a seperate
    > query for everyone that would be accessing the data inside the database?

    Or
    > is there a way to automate this?
    >
    > Again, thanks for the response all
    >
    > "Douglas J. Steele" wrote:
    >
    > > You'd have to use a query to let them get at the data, as opposed to

    using
    > > the table directly.
    > >
    > > --
    > > Doug Steele, Microsoft Access MVP
    > > http://I.Am/DougSteele
    > > (no e-mails, please!)
    > >
    > >
    > >
    > > "mattymatt79" <mattymatt79@discussions.microsoft.com> wrote in message
    > > news:635B5792-4700-450A-9544-A34ED79838FA@microsoft.com...
    > > > Ok great post and thank you, but I'm still not sure if using the

    access
    > > > users
    > > > and groups would do exactly what I want them to do.
    > > >
    > > > Example
    > > > User A (general user) enters in customer information
    > > > User B (general user) enters in customer information
    > > >
    > > > Wouldn't even with security since they are the exact table go to the

    exact
    > > > same security setting? Meaning that user A could view user B's
    > > > information?
    > > >
    > > > Also User C (manager) needs to be able to view all info, which is

    simple,
    > > > I
    > > > just make a new group for them, but what about User A and B?
    > > >
    > > >
    > > > "Douglas J Steele" wrote:
    > > >
    > > >> You can use Access User Level Security to achieve most of what you're
    > > >> looking for, but Access doesn't interact with Active Directory:

    you'll
    > > >> have
    > > >> to create new user ids within Access, and the users will have to

    maintain
    > > >> separate passwords for those new ids.
    > > >>
    > > >> --
    > > >> Doug Steele, Microsoft Access MVP
    > > >> http://I.Am/DougSteele
    > > >> (no e-mails, please!)
    > > >>
    > > >>
    > > >> "mattymatt79" <mattymatt79@discussions.microsoft.com> wrote in

    message
    > > >> news:E013C795-6872-40C6-B27C-F1018A5D439E@microsoft.com...
    > > >> > ok,
    > > >> > well I have a pretty decent grasp on how access works, and what i

    want
    > > >> > to
    > > >> do.
    > > >> > I have the database pretty much done and the forms completed I just
    > > >> > have
    > > >> one
    > > >> > last thing to accomplish and i dont know how to really finish it

    up.
    > > >> >
    > > >> > Ill explain the situation.
    > > >> > I have a database that tracks people and contacting them.
    > > >> >
    > > >> > Is there a way to lock down who can access what with Active

    Directory
    > > >> based
    > > >> > on thier login?
    > > >> >
    > > >> > Also, searching, as in say a manager can search all aspects of
    > > >> > information
    > > >> > on the database, but the person who entered it can only access

    thier
    > > >> > information?
    > > >> >
    > > >> > Also can it be that the person who entered it can not delete it,

    but
    > > >> > the
    > > >> > manager can manipulate all the data?
    > > >> >
    > > >> > I have the table done, just not the search aspect of it.
    > > >> >
    > > >> > Also if there was a way to just put in everyone that was accessing

    the
    > > >> > database could then instead lock down what search aspects were

    involved
    > > >> with
    > > >> > the database then?
    > > >>
    > > >>
    > > >>

    > >
    > >
    > >
     

Share This Page