[AccessD] SPAM-LOW: Re: Access 2007 accde User Security

jwcolby jwcolby at colbyconsulting.com
Wed Jan 27 07:49:11 CST 2010


 > Unfortunately for me, it was after I had written most of the code for my main program.

My good friend Shamil poked and prodded me until I finally took the time to learn classes and 
withevents.  AFAICT Shamil subsequently abandoned Withevents in Access (there were still big issues 
with them back then) but I continue to use them.

I really started learning them somewhere around the year 2000, and I had written my entire first 
framework without them.  I started completely over on a brand new version of my framework in order 
to incorporate my new found powers, so I certainly understand your pain.

 > When I briefly looked at all the "stuff" in their I was like HOLY COW, what in the **** could all 
this possibly do with LWS ... ;-)

PLS (Presentation Level Security) as I prefer to call it now is currently a "program it" security 
system.  IOW if you want to enable security on an object you have to write a line of code about that 
object.  While that works it is clumsy and raises issues of discovering what objects in the database 
have been secured.

All of that "other stuff" is my first attempt at defining a "table driven" PLS.  Instead of writing 
code for each object to be secured, the "right" way to do this is to have a form / control table set 
where you simply place the name of the form in a table and then a table to define what groups can do 
what things in that form.

Forms can be opened, records in forms added, deleted, and edited.

Another table pair holds controls and what groups can do what with controls.

Controls can be viewed, enabled / disabled and locked / unlocked.

If you make the system table driven like that then setting up security becomes much more organized, 
a "security officer" can set up the security, and you can generate reports about the security.

So PLS today is but a shadow of its potential.  I would LOVE to take it to the next level but 
working alone I find it difficult to implement all of the things I can envision.

John W. Colby
www.ColbyConsulting.com


Robert wrote:
> John,
>  Ok that helped a bunch, because there's a lot of 'other' stuff in that
> db.... ;-) 
> 
> BIG Thanks to you, I have been working with classes ever since your very
> first class introduction several years ago, and can really appreciate the
> beauty in function that a class object provides. 
> 
> Unfortunately for me, it was after I had written most of the code for my
> main program. For the last couple of years I've been slowly breaking it down
> into much more powerful class objects.
> 
> When I briefly looked at all the "stuff" in their I was like HOLY COW, what
> in the **** could all this possibly do with LWS ... ;-)
> 
> Thanks Again
> 
> WBR
> Robert
> 
> PS: The Administrator credentials appear to be incorrect (the password)




More information about the AccessD mailing list