[AccessD] Never Take a job for a friend (Three leveldesignquestion)

Charlotte Foust cfoust at infostatsystems.com
Mon Jul 2 12:03:46 CDT 2007


Is there some reason NOT to use Access security for this?  It still
works in 2003 format.

Charlotte Foust 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark A Matte
Sent: Monday, July 02, 2007 8:51 AM
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] Never Take a job for a friend (Three
leveldesignquestion)

Joe,

I have a db that allows multiple people can add notes.  No One can edit
old notes.  Each note has a DT stamp,User_ID, and note type.  The notes
are added via an unbound box.

If I wanted to impliment what you described...I would probably add a
field to my notes table...and along with DTS and USER...I would add a
User_Type to the notes.

Dispatchers =D
Field supervisor =F
manager =M
executive notes=E

Each time a note is created the User_Type would be populated with one of
the above depending on the users level of access.

One the form/subform displaying the notes...I would change the data
source via VBA(depending on user), the 'where' clause specifically.  If
a dispatcher is logged in..."where User_Type ='D'"...since Dispatchers
cannot add notes...none would be returned.  See below:

EXAMPLE WHERE CLAUSES
Dispatchers =where User_Type ='D'
Field supervisor =where User_Type ='D' or User_Type ='F'
manager =where User_Type ='D' or User_Type ='F' or User_Type ='M'
executive notes=where User_Type ='D' or User_Type ='F' or User_Type ='M'
or User_Type='E'

Just a thought...

Good Luck,

Mark A. Matte

>From: "Arthur Fuller" <fuller.artful at gmail.com>
>Reply-To: Access Developers discussion and problem 
>solving<accessd at databaseadvisors.com>
>To: "Access Developers discussion and problem 
>solving"<accessd at databaseadvisors.com>
>Subject: Re: [AccessD] Never Take a job for a friend (Three level
>designquestion)
>Date: Sun, 1 Jul 2007 13:07:49 -0400
>
>Minor addendum, perhaps obvious. If a dispatcher is looking, hide the 
>Notes, period.
>
>Arthur
>
>
>On 7/1/07, Arthur Fuller <fuller.artful at gmail.com> wrote:
> >
> > I think that some of the respondents so far kind of missed your 
> > requirements, Joe (or perhaps the beer I'm enjoying for Canada has 
> > had
>more
> > effect than I anticipated).
> >
> > You actually have only 3 meaningful user levels, since dispatchers 
> > are powerless. The other three make a grid like this:
> >
> >               Sup       Mgr       Exec
> > Sup          W         X            X
> > Mgr          R          W           X
> > Exec        R          R            W
> >
> > Where R means Read, W means Write, and X means neither. If the user
>table
> > contained a 3-char column with each horizontal combination written 
> > as a string (i.e. WXX, RWX and RRW) then the OnCurrent event can 
> > examine the current row's notes field and act accordingly.
> >
> > This demands of course that the Notes rows be tagged with UserLevel
>column
> > (S, M or E).
> >
> > If a Sup is looking and the current Notes.UserLevel column contains 
> > M or E, hide the Notes.
> > If a Mgr is looking and the current Notes UserLevel contains S, then

> > Notes.enabled = False; if the Notes UserLevel is E, then hide the
Note.
> > If an Exec is looking, and the current Notes UserLevl contains S or 
> > M, Notes.enabled = False, else Notes.Enabled = True.
> >
> > I think that covers it.
> >
> > hth,
> > Arthur
> >
> >
> > This problem will be much easier to deal with if the notes are 
> > presented in single-form fashion rather than datasheet. That said,
> >
> >
> >  On 6/30/07, Joe Hecht <jmhecht at earthlink.net> wrote:
> > >
> > > It is simple. Ya Right
> > >
> > >
> > >
> > > I am righting a poor mans HR program. There are four user levels.
> > > Dispatchers can not do notes, can not see notes. Field supervisor 
> > > can write notes. Can not see manager or executive notes.  Managers

> > > can write notes, can read Field supervisor notes, not edit them or

> > > see executive notes.
> > > Executives can write theirs, see but not edit all other notes.
> > >
> > >
> > >
> > > Notes are many notes to one employee.
> > >
> > >
> > >
> > > How do I do notes so people see them in chronological order? If I 
> > > do three sub tables how would I get all notes to same point. One 
> > > employee can have multiple incidents good and bad in their record.

> > > How would I get all three levels of notes to same incident?
> > >
> > >
> > >
> > > Ya all know where I am spending my sat night.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Joe Hecht
> > >
> > > jmhecht at earthlink.net
> > >
> > >
> > >
> > > --
> > > AccessD mailing list
> > > AccessD at databaseadvisors.com
> > > http://databaseadvisors.com/mailman/listinfo/accessd
> > > Website: http://www.databaseadvisors.com
> > >
> >
> >
>--
>AccessD mailing list
>AccessD at databaseadvisors.com
>http://databaseadvisors.com/mailman/listinfo/accessd
>Website: http://www.databaseadvisors.com

_________________________________________________________________
Don't miss your chance to WIN $10,000 and other great prizes from
Microsoft Office Live
http://clk.atdmt.com/MRT/go/aub0540003042mrt/direct/01/





More information about the AccessD mailing list