By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,497 Members | 2,113 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,497 IT Pros & Developers. It's quick & easy.

Each Access security group can have only one password?

P: n/a
When using Access security can each group have only one password?
So all members of the group have the same and/or one password?
Then in order to have each member of a group have their own password
then you would need a group for each member?

Feb 13 '07 #1
Share this Question
Share on Google+
3 Replies


P: n/a
<to*******@msn.comwrote in message
news:11**********************@a75g2000cwd.googlegr oups.com...
When using Access security can each group have only one password?
So all members of the group have the same and/or one password?
Then in order to have each member of a group have their own password
then you would need a group for each member?
I was not aware that a group has a password at all.....
So all members of the group have the same and/or one password?
No, each user that logs on has their own password. You then assign the
groups to the user.

So, users become members of groups....or, a better ways is to say that YOU
assign
each me (user) to a particular group.

There is no passwords involved in assigning those groups to each member.
(you have to have admim privileges to make those assignments).

So, you might assign some users to be a member of the SalesReprot group, and
they would be the only ones
that could view reports that are a member of that SalesReprot group.

If you always assigning users to member groups, then you NEVER actually put
the users names into the actual mdb.
Thus, you can freely deploy new updates to your clients, and their existing
security settings will NOT be lost
when you deploy that new front end to them. However, the instant you start
assigning actual users to actual forms,
or report (or any object), then when you deploy a new update, then those
setting the customer made will be lost
(assuming you are developing in a different location, or "off site" from
where the software is being used - this
also assume they are not making new "groups"). You should as a general rule
site down and make the groups
so that during development..as you add a new report, or whatever..you assign
it to the particular group of your
choice. Then as you add new users, you assign what user groups they belong
to (sales group, accounting group
....whatever you like). Take a look at the following screen shots to see what
I mean by sitting down and making some user
groups.

http://www.members.shaw.ca/AlbertKal...erFriendly.htm

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com
Feb 13 '07 #2

P: n/a
Hello,

I have been asked to make modifications in a database but I am not
very familiar with Access. This database is accessed over the network,
by many concurrent users. Working directly in the production database,
apart from being bad practice in general I suppose:), is therefore not
an option. But taking it down isn't either. What I am looking for is
some pointers to sites/books that can supply me with guidelines on how
to best go about.

tia,
arno
Feb 13 '07 #3

P: n/a
sorry sorry, wrong shortcut key, was meant to be new thread - arno
Feb 13 '07 #4

This discussion thread is closed

Replies have been disabled for this discussion.