Robert
robert at servicexp.com
Tue Jan 26 10:24:03 CST 2010
Obtuse..... lol.. I would certainly be willing to document it, well at least the parts I understand, then I would need your help... :-). I would imagine, the time to document it would be less than the time to roll my own and get it working. I would also be willing to create a small help file for it. WBR Robert -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby Sent: Tuesday, January 26, 2010 8:50 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] SPAM-LOW: Re: Access 2007 accde User Security If I donate this library to Database Advisors Inc would anyone be willing to form a working group to work on it / document it? The application works (quite well) and I use it in several different databases but it is undocumented. As William will tell you, when I do write documentation it is ... "obtuse" is the phrase he used. John W. Colby www.ColbyConsulting.com Robert wrote: > Sounds like a pretty good game plan. Do you have this as a Demo on your > site? I would be very interesting in the table design... > > > Thank You John! > > 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 4:55 PM > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] SPAM-LOW: Re: Access 2007 accde User Security > > 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 >>> >>> >>> -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com