jwcolby
jwcolby at colbyconsulting.com
Mon Jan 25 15:55:05 CST 2010
I use a class system and caches. I create three tables: usystblLWSUsers usystblLWSGroups usystblLWSUserGroups I create a class for each of these objects, plus a cache that is the supervisor that loads each of these. I have a module that holds a global function for getting the pointer to the supervisor, as well as functions to initialize and tear down the supervisor. All of this is created out in a library - C2DbLWS.mda which is referenced by anything that needs the security. Essentially your startup code instantiates the supervisor which loads the three tables into classes and stores them into collections. Once loaded the supervisor has methods such as UserInGroup(idUser, IDGrp) as boolean. It was not a trivial undertaking, but once written it pretty much just works. John W. Colby www.ColbyConsulting.com Robert wrote: > Can you give / share any pointers? > > WBR > Robert > > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby > Sent: Monday, January 25, 2010 12:49 AM > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] SPAM-LOW: Access 2007 accde User Security > > I have rolled my own. I have used it for years. > > John W. Colby > www.ColbyConsulting.com > > > Robert wrote: >> Those who have moved to the newer 2007 db container what are you using for > a >> lightweight user authentication system? >> >> Has anyone rolled their own? If memory serves me, I believe John Colby > was >> creating his own several years ago. >> >> >> >> WBR >> Robert >> >> >>