Re: Setting up Authorizations for on-Form data entry: Advice requ

Thanks Ian,
I'll read this over this weekend. Again, thanks for your time.
--
GmH


"IanOxon via AccessMonster.com" wrote:

Hi Gavin,

Yes I was talking about logging onto the database. But if your "certicate
number" is the primary key field (unique record identifier) then the table
you've constructed and adapting the example code, will help you achieve you
initial objectives.

I'd still advise you to look into Jet Security (even at this early stage) -
at the moment you're using it without realising it. The default system.mdw
file your using comes with all access installations and when you create a new
database all members of the default Users group have adminstrative
permissions for all existing database objects and ones that will be created
later. Newly created users are automatically added to the Users group (which
cannot be deleted). These two things mean that anybody with access to your
database file can edit or delete database objects, and/or records until you:

1. Create a new workgroup information file (.mdw) and alter permissions of
the Users group
2. Start creating groups and users of your own with specific permissions.

It also means a password logon - no bad thing as this helps secure any
sensitive data.

This may seem like a daunting task, but you're already halfway there because
you're thinking about what people should be allowed access to which database
objects.


All The Best


Ian

RoadKyng wrote:
Greetings Ian
thanks for the time you spent on a response. I am going to print it out and
study for awhile, then get back to you. One thing, my original try did not
look at the user's login id as far as the database is concerned. I assume you
mean a login when they open the database. I have not set security up yet as I
am still in the developement stage (also, I'm no pro at this so I did not
think that far ahead).

What I have is a table that holds people and a permissions subtable that has
check boxes of what they can do. They are tied together by a certificate
number. When useing the form in my original post, when at the field where an
authorization is needed to perform the function a popup asks for the
Certificate number and checks against the subtable of permissions. If = yes
then the form contues. At least that's where I am trying to go.

gavin hill
If I read this right what you want is to allow/restrict access to bound forms
and the related datasets (Form RecordSource queries and tables) based on the
[quoted text clipped - 133 lines]

gavin

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-formscoding/200603/1

.

Relevant Pages

  • Re: security only works on my PC
    ... still able to enter Explorer and enter the database without a login. ... checked the permissions box and the Users group has no permissions on ... Open it using your shortcut and log in. ... Click on the Groups option and select the Users Group. ...
    (microsoft.public.access.security)
  • Re: Security without signon
    ... >have not split my database and at this point would prefer not to. ... >have set up the form to run off a RWOP query, and I have removed all access ... >to the tables from the Users Group. ... give limited permissions to the Users group. ...
    (microsoft.public.access.security)
  • Re: security only works on my PC
    ... I checked the permissions box and the Users group has no ... Open/Run and open exclusive on database object ... Open it using your shortcut and log in. ... Click on the Groups option and select the Users Group. ...
    (microsoft.public.access.security)
  • Re: Becoming the Owner
    ... so you can open the database while joined to ... and check the permissions for the Database object type. ... remove the permissions on all objects for the Users group. ... workgroup file. ...
    (microsoft.public.access.security)
  • Re: would it be wise???
    ... The Users group should not have any permissions to any object in the ... > group permission to open/run the database, ... >>> if passwords are stored in the workgroup file, ...
    (microsoft.public.access.security)