[AccessD] Never Take a job for a friend (Threeleveldesignquestion) Looking for AD

    Yes Joe !  I am now on line (it is 09-15 Hrs Indian Standard Time).

    I shall try to put together a sample db, meeting all your requirements. However, in order to make it generic and suitable for larger organizations, the additional feature of ChainOfCommand integrity would also be included.

Best wishes,
A.D.Tejpal
adtejpal at gmail.com
-------------------------

  ----- Original Message ----- 
  From: Joe Hecht 
  To: 'Access Developers discussion and problem solving' 
  Sent: Tuesday, July 03, 2007 07:33
  Subject: Re: [AccessD] Never Take a job for a friend (Threeleveldesignquestion) Looking for AD


  Hi AD,

  It is 7:00 Pacific. Are you on line?

  Joe Hecht
  jmhecht at earthlink.net

  -----Original Message-----
  From: accessd-bounces at databaseadvisors.com
  [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of A.D.TEJPAL
  Sent: Monday, July 02, 2007 11:30 AM
  To: Access Developers discussion and problem solving
  Subject: Re: [AccessD] Never Take a job for a friend (Three
  leveldesignquestion)

  Joe,

      It might be desirable to enforce ChainOfCommand discipline as well. For example One chief executive can have more than one managers. Each of these managers has more than one supervisors. Each supervisor in turn has more than one employees under his control.

      Manager A can see all the notes recorded by supervisors for employees under his command only. Similarly only those in the chain of command for a particular employee can record notes for that employee.

      For this, recursive joins would be necessary. Would you like a solution to be explored on these lines ?

  Best wishes,
  A.D.Tejpal
  ---------------

    ----- Original Message ----- 
    From: Joe Hecht 
    To: 'Access Developers discussion and problem solving' 
    Sent: Sunday, July 01, 2007 04:38
    Subject: [AccessD] Never Take a job for a friend (Three level
  designquestion)


    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