[AccessD] Never Take a job for a friend

Lately I've been using API calls to get the username they are logged on to 
the computer with...then have a table listing potential users and their 
level of access.  Just remember to leave someone access to update this 
table.

Mark

>From: "Charlotte Foust" <cfoust at infostatsystems.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
>Date: Tue, 3 Jul 2007 08:20:17 -0700
>
>It needn't be that draconian, and security isn't all that hard.  How
>could it be any harder than keeping track of who is supposed to have
>which permissions entirely through code?
>
>It would save a lot of work for Joe if there were simply 3, or however
>many, user groups with specific permissions.  Then a simple login to the
>application would handle the details.  You could even just create logins
>for each group and not go any further into personal logins.  People
>being what they are, sooner or later someone would find out the other
>logins and try them "for fun", of course.
>
>Charlotte Foust
>
>-----Original Message-----
>From: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Robert L.
>Stewart
>Sent: Tuesday, July 03, 2007 7:38 AM
>To: accessd at databaseadvisors.com
>Subject: Re: [AccessD] Never Take a job for a friend
>
>Since it is for a "friend," I would say
>absolutely do not use security. Personally, I would not want to get
>sucked into having to maintain it.
>
>Robert
>
>At 09:28 AM 7/3/2007, you wrote:
> >Date: Mon, 2 Jul 2007 10:03:46 -0700
> >From: "Charlotte Foust" <cfoust at infostatsystems.com>
> >Subject: Re: [AccessD] Never Take a job for a friend (Three
> >         leveldesignquestion)
> >To: "Access Developers discussion and problem solving"
> >         <accessd at databaseadvisors.com>
> >Message-ID:
> >
><F55048AF7E974F429BB24597D7355EEA4BA25A at INFOSERVER04.infostat.local>
> >Content-Type: text/plain;       charset="us-ascii"
> >
> >Is there some reason NOT to use Access security for this?  It still
> >works in 2003 format.
> >
> >Charlotte Foust
>
>
>--
>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

_________________________________________________________________
http://newlivehotmail.com