Tobi,
I borrowed your code and implemented a
user level table then added code to each form to allow access based on user
level.
I also added a user level column to a
standard switchboard table and form to display available command buttons based
on user level.
I had to remove the user delete code in
order to track changes and allow multiple users simultaneous access to the db.
Carl
From: AccessDevelopers@yahoogroups.com [mailto:AccessDevelopers@yahoogroups.com] On Behalf Of Hoffman, Tobi K (DYS)
Sent: Wednesday, December 21, 2005
11:00 AM
To: AccessDevelopers@yahoogroups.com
Subject: RE: [AccessDevelopers]
Re: Security
I use buttons to launch forms
and reports, and make them visible or not
in the Form_Open event that contains the buttons,
based on user level.
And since I hide the database window in the
Startup options, the user
doesn't see them; if necessary, there are further
measures you can take
to keep their fingers out of places they don't
belong.
And generally, yes, the invisible form works
well. I've also used it to
make sure people don't sneak in and try opening
forms from the database
window -- in one case where that had been
happening, I made it
automatically shut the database down.
Tobi
-----Original Message-----
From: AccessDevelopers@yahoogroups.com
[mailto:AccessDevelopers@yahoogroups.com]
On Behalf Of Elena
Sent: Wednesday, December 21, 2005 10:45 AM
To: AccessDevelopers@yahoogroups.com
Subject: [AccessDevelopers] Re: Security
Ok, so do I have to go in to that code and specify
which forms,
reports, tables, etc. are allowed for each user
level?
Does using the invisible form work better than the
Dlookup?
Thanks so much!
--- In AccessDevelopers@yahoogroups.com,
"Hoffman, Tobi K \(DYS\)"
<[EMAIL PROTECTED]> wrote:
>
> I had to look at this myself to see how this
DB did things! When
> someone logs in, their info, including user
level, gets stored in
> t_Current. When a form opens, its
OnOpen event can look at the
user
> level in that table, and based on that, set
Visible=False for any
> controls that they're not supposed to be
using.
>
> In more recent DBs, I put that data onto an
invisible form,
frmCurrent,
> and refer to Forms!frmCurrent!txtUserLevel
and use that instead of
a
> Dlookup.
>
> Tobi
>
> -----Original Message-----
> From: AccessDevelopers@yahoogroups.com
> [mailto:AccessDevelopers@yahoogroups.com]
On Behalf Of Elena
> Sent: Wednesday, December 21, 2005 7:56 AM
> To: AccessDevelopers@yahoogroups.com
> Subject: [AccessDevelopers] Re: Security
>
>
> I'm just using the Access security as I am
still new to Access and
> it's functions. I've taken a look at this DB
Tobi and I have a
> couple of questions:
> How do you set up what the users can or can't
see/edit? I noticed
> that when I set myself up as Administrator it
allowed some things
> but not others but I couldn't find (or maybe
I'm not recognizing)
> where you set up those rules.
>
> Also, you have an ActiveXCtl76 on one of your
forms and I was
> wondering what it does.
>
> Thanks for your help.
>
>
> --- In AccessDevelopers@yahoogroups.com,
"Tobi Hoffman"
> <[EMAIL PROTECTED]> wrote:
> >
> > I put up a file, AccessLoginDBs.zip, in
the Demos and Sample
Files
> section a
> > few years ago with code to log in
users. The Access security has
> too many
> > pitfalls and problems, so I only used it
in one job way back
years
> ago.
> >
> > Tobi
> >
> > _____
> >
> > From: AccessDevelopers@yahoogroups.com
> > [mailto:AccessDevelopers@yahoogroups.com]
On Behalf Of Carl Beck
> > Sent: Wednesday, December 21, 2005 2:49
AM
> > To: AccessDevelopers@yahoogroups.com
> > Subject: RE: [AccessDevelopers] Security
> >
> >
> >
> > How do you have it secured? Your own
code or Access User
> permissions.
> >
> > User permissions utilizes a MDW file on
the local machine unless
> otherwise
> > directed, if the file is not there then
the db might not be
> secured.
> >
> > If you are using SQL as the backend then
what security is being
> used there
> > SQL or NT?
> >
> > Access always calls the system.mdw file
located in the root dir.
> If you set
> > the permissions on your machine then
move it those permissions
> don't move to
> > the new machine.
> >
> > I find it is best to create a self
contained user permissions
> table as well
> > as a log in form.
> >
> > Someone has a sample up for download
somewhere I just don't
> remember where.
> >
> >
> >
> > Carl
> >
> >
> >
> > _____
> >
> > From: AccessDevelopers@yahoogroups.com
> > [mailto:AccessDevelopers@yahoogroups.com]
On Behalf Of Jose Luis
> Jr Mora Jr
> > Sent: Wednesday, December 21, 2005 12:59
AM
> > To: AccessDevelopers@yahoogroups.com
> > Subject: Re: [AccessDevelopers] Security
> >
> >
> >
> > Are you having the users go through the
MDW file?
> >
> > Elena <[EMAIL PROTECTED]> wrote:
> >
> > Hi all. Thanks for the help on the counting
days question now I
> have
> > another.
> >
> > I have created users for my DB and am
ready for folks to try it
> out.
> > The problem is when they open the
program on their computers (the
> file
> > is in a shared network drive) they are
not prompted for user name
> and
> > password. When I open it on my computer
it works just fine. Is
> there
> > something else I have to do in order for
the users to be
prompted?
> >
> > Thanks!!
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Please zip all files prior to uploading
to Files section.
> >
> >
> >
> >
> >
> > SPONSORED LINKS
> > Microsoft
> > <http://groups.yahoo.com/gads?
>
t=ms&k=Microsoft+access+developer&w1=Microsoft
> >
>
+access+developer&w2=Microsoft+access+help&w3=Microsoft+access+databa
> se&w4=M
> >
>
icrosoft+access+training&w5=Microsoft+access+training+course&w6=Micro
> soft+ac
> >
cess+programming&c=6&s=193&.sig=d-CjBIrYOH9NCKHYFeGZJA> access
> developer
> > Microsoft
> > <http://groups.yahoo.com/gads?
>
t=ms&k=Microsoft+access+help&w1=Microsoft+acce
> >
>
ss+developer&w2=Microsoft+access+help&w3=Microsoft+access+database&w4
> =Micros
> >
>
oft+access+training&w5=Microsoft+access+training+course&w6=Microsoft+
> access+
> >
programming&c=6&s=193&.sig=crx-d4AAhdklv_VozGVAUw> access help
> Microsoft
> > <http://groups.yahoo.com/gads?
> t=ms&k=Microsoft+access+database&w1=Microsoft+
> >
>
access+developer&w2=Microsoft+access+help&w3=Microsoft+access+databas
> e&w4=Mi
> >
>
crosoft+access+training&w5=Microsoft+access+training+course&w6=Micros
> oft+acc
> >
ess+programming&c=6&s=193&.sig=qg2hDuQNweByMCX0NU7cEA> access
> database
> > Microsoft
> > <http://groups.yahoo.com/gads?
>
t=ms&k=Microsoft+access+training&w1=Microsoft+
> >
>
access+developer&w2=Microsoft+access+help&w3=Microsoft+access+databas
> e&w4=Mi
> >
>
crosoft+access+training&w5=Microsoft+access+training+course&w6=Micros
> oft+acc
> >
ess+programming&c=6&s=193&.sig=bLZHqTqWUQny609X1OkmNA> access
> training
> > Microsoft
> > <http://groups.yahoo.com/gads?
>
t=ms&k=Microsoft+access+training+course&w1=Mic
> >
>
rosoft+access+developer&w2=Microsoft+access+help&w3=Microsoft+access+
> databas
> >
>
e&w4=Microsoft+access+training&w5=Microsoft+access+training+course&w6
> =Micros
> > oft+access+programming&c=6&s=193&.sig=d8GQXfQW3RZ64rOfzIMo8A>
> access
> > training course
Microsoft
> > <http://groups.yahoo.com/gads?
>
t=ms&k=Microsoft+access+programming&w1=Microso
> >
>
ft+access+developer&w2=Microsoft+access+help&w3=Microsoft+access+data
> base&w4
> >
>
=Microsoft+access+training&w5=Microsoft+access+training+course&w6=Mic
> rosoft+
> >
access+programming&c=6&s=193&.sig=iXDlL79-kkgjv6fLyFu3Sg> access
> programming
> >
> >
> > _____
> >
> > YAHOO! GROUPS LINKS
> >
> >
> >
> > * Visit
your group "AccessDevelopers
> > <http://groups.yahoo.com/group/AccessDevelopers>
" on the web.
> >
> >
> > * To
unsubscribe from this group, send an email to:
> >
[EMAIL PROTECTED]
> >
<mailto:[EMAIL PROTECTED]
> subject=Unsubscribe>
> >
> >
> > * Your use
of Yahoo! Groups is subject to the Yahoo! Terms of
> Service
> > <http://docs.yahoo.com/info/terms/>
.
> >
> >
> > _____
> >
>
>
>
>
>
>
>
>
> Please zip all files prior to uploading to
Files section.
> Yahoo! Groups Links
>
Please zip all files prior to uploading to Files
section.
Yahoo! Groups Links
Please zip all files prior to uploading to Files section.
YAHOO! GROUPS LINKS
