Re: Username and Usergroup

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: TK (sprdthword_at_hotmail.com)
Date: 09/20/04 

Date: Mon, 20 Sep 2004 15:54:23 +0300

69 Camaro,
No - I wasn't disagreeing with you at all and I fully agree with the
methodology you have proposed.
My question was actually for jokobe - as to why he/she feels they need to
trap this in the first place. I can see if they are setting permissions on
the fly through code - and maybe that is what is happening, but the original
post just seemed as though they wanted to know who was in the allowed
group(s) and who wasn't.
TK

"'69 Camaro" <ForwardZERO_SPAM.To.69Camaro@Spameater.orgZERO_SPAM> wrote in
message news:urRw2mwnEHA.2388@TK2MSFTNGP10.phx.gbl...
> Hi, TK.
>
> > I'm curious - what is the point of this function? If the user is not in
> the
> > group that has the permissions to run the query in question, or open the
> > form, etc. - they already won't be able to do so
>
> You have a valid point about the security permissions for running queries
or
> opening forms. However, Jokobe didn't ask how to control these
operations.
> While you may disagree with me, after reading the request I interpreted
> Jokobe to be requesting information for how to capture the user name and
> group name to _use_ for some queries and forms:
>
> > > > Within the database I
> > > > do need the username and the usergroup for some
> > > > queries/and forms. Is there a chance to catch the username
> > > > when starting the database?
>
> Access developers who need to customize database applications require a
lot
> more flexibility than just the ability to limit who runs which queries or
> who opens which forms. These two functions I posted below allow much more
> granularity of the security permissions assigned and help prevent
> duplication of development and maintenance efforts.
>
> For example, a form that has multiple inputs from various users of two
> groups, "Data_Input" and "Supervisors," should have sufficient permissions
> to enable both groups to open the form. However, the form's "Approved"
> field should be locked for the "Data_Input" users so that they can't make
> changes to it. If a developer didn't have the ability to determine
whether
> the current user was not a member of the "Supervisors" group in order to
> lock that field when the form opens, then there would have to be two
> different forms, one for members of the Data_Input" group (which lacks an
> "Approved" field) and another one for members of the "Supervisors" group
> (which displays all fields). Having two separate forms doubles the
> developer's efforts required to make changes to the form, so this is not
> desirable.
>
> Queries can also be customized by filtering records from tables that
> multiple groups are permitted to view, including when certain fields are
not
> necessary for members of some of the groups. Instead of creating multiple
> queries that are nearly identical, one for each group, a single query can
be
> created and filtered with the WHERE clause, HAVING clause, and/or IIF( )
> function.
>
> > So why are you trapping that when opening the db?
>
> I didn't mention it, but with the functions I posted below, there's no
need
> to trap the user name or user group upon opening the database. These
> functions will return the correct values at any time while the database
> application is running, so there's no need to capture and save them for
> later use.
>
> Does this explanation satisfy your curiosity?
>
> Gunny
>
> See http://www.QBuilt.com for all your database needs.
> See http://www.Access.QBuilt.com for Microsoft Access tips.
>
> (Please remove ZERO_SPAM from my reply E-mail address, so that a message
> will be forwarded to me.)
>
>
> "TK" <sprdthword@hotmail.com> wrote in message
> news:O56HR4vnEHA.3680@TK2MSFTNGP10.phx.gbl...
> > I'm curious - what is the point of this function? If the user is not in
> the
> > group that has the permissions to run the query in question, or open the
> > form, etc. - they already won't be able to do so and Access will gladly
> let
> > them know.
> > So why are you trapping that when opening the db?
> > Just wondering.
> > TK
> >
> > "'69 Camaro" <ForwardZERO_SPAM.To.69Camaro@Spameater.orgZERO_SPAM> wrote
> in
> > message news:%23hL3I$unEHA.744@TK2MSFTNGP10.phx.gbl...
> > > Hi.
> > >
> > > After the user has successfully logged into the secure database, use
the
> > > following function to determine the user's UserID:
> > >
> > > CurrentUser( )
> > >
> > > Since users are often members of multiple groups, it would probably be
> > > better to find out whether the current user was a member of a specific
> > group
> > > that has the permissions to run a certain query or open a certain
form.
> > You
> > > can use code such as the following to determine whether a user is a
> member
> > > of a specific group:
> > >
> > > '=======================================
> > > ' Function: isMemberOfGrp( )
> > > ' Returns True if the user is in the group.
> > > ' Usage: isMemberOfGrp(CurrentUser(), "Admins")
> > > '=======================================
> > >
> > > Public Function isMemberOfGrp(sUserName As String, sGrpName As String)
> > >
> > > On Error Resume Next
> > >
> > > Dim junk As String
> > >
> > > junk = DBEngine(0).Users(sUserName).Groups(sGrpName).Name
> > >
> > >
'-------------------------------------------------------------------
> > > ' Determine whether checking this Property
> > > ' caused an error or not.
> > >
'-------------------------------------------------------------------
> > >
> > > If (Err.Number = 0) Then
> > > isMemberOfGrp = True
> > > Else
> > > isMemberOfGrp = False
> > > End If
> > >
> > > Err.Clear
> > >
> > > End Function
> > >
> > > HTH.
> > >
> > > Gunny
> > >
> > > See http://www.QBuilt.com for all your database needs.
> > > See http://www.Access.QBuilt.com for Microsoft Access tips.
> > >
> > > (Please remove ZERO_SPAM from my reply E-mail address, so that a
message
> > > will be forwarded to me.)
> > >
> > >
> > > "jokobe" <anonymous@discussions.microsoft.com> wrote in message
> > > news:447f01c49ee9$837cf6b0$a601280a@phx.gbl...
> > > > Hi ng,
> > > >
> > > > when starting a secure database(ACC2000) the user have to
> > > > give his username and his password. Within the database I
> > > > do need the username and the usergroup for some
> > > > queries/and forms. Is there a chance to catch the username
> > > > when starting the database?
> > > >
> > > > thanks in advance
> > > >
> > > > jokobe
> > >
> > >
> >
> >
>
>

Relevant Pages

  • Re: Setting up user group that can create and save select queries
    ... 'Run with owner permissions' - See www.jmwild.com/RWOP.htm for more information. ... Put your users in one of the wizard-created groups, as well as the group you created for them, and they'll be able to save their queries. ... Give the users modify permissions on the query to change the SQL property in code. ... The application database used to enter and update the data; ...
    (microsoft.public.access.security)
  • Re: RWOP /table permissions question
    ... Look in the security FAQ. ... without them needing permissions on the tables. ... Microsoft Access MVP ... Now base all your SQL statements on these queries rather than ...
    (microsoft.public.access.security)
  • Re: Setting up user group that can create and save select queries
    ... You are having this problem because of a bug with the security wizard. ... Put your users in one of the wizard-created groups, as well as the group you created for them, and they'll be able to save their queries. ... Give the users modify permissions on the query to change the SQL property in code. ... The application database used to enter and update the data; ...
    (microsoft.public.access.security)
  • RE: Best way to share
    ... > I used this article to setup the security: ... > tables in the backend, the queries, forms, reports, etc. ... > the same security file but have permissions set differently. ...
    (microsoft.public.access.security)
  • Re: Query Security
    ... You could also dynamically create the queries on opening of the form & Add ... With OWNER permissions etc ... The best way as suggested is to disallow users the DB window ie disable ... >>Microsoft Access MVP ...
    (microsoft.public.access.security)