Update Access Security With VBA

  • Thread starter Thread starter Eric
  • Start date Start date
E

Eric

I've got a multiuser Access 2002 DB. Up to this point,
I've handled security myself with a capabilities table
and code. This has served okay as the capabilities
variations are somewhat complex with many influencing
what is displayed and what is hidden on forms. As well,
it allows me to shell the users from the somewhat cryptic
Access built-in security so they can do their own
maintenance with proper authorization.

I now find a need to invoke Access built-in security but
I'd still like to shell the users. I assume I have to
manipulate the mdw file. I tried opening it but it won't
show me any tables, much less how they are structured.

I haven't found any clues on how to do this with VBA. Is
there any way this can be done?

TIA for any advise....Eric
 
I've got a multiuser Access 2002 DB. Up to this point,
I've handled security myself with a capabilities table
and code. This has served okay as the capabilities
variations are somewhat complex with many influencing
what is displayed and what is hidden on forms.
Click to expand...

But if you do not use Access security to protect the capabilities table,
users can probably go to that table & change it manually, no? It's a "Catch
22" situation. Without using Access security, it's difficult to protect any
tables that you use for custom security schemes.

As well,
it allows me to shell the users from the somewhat cryptic
Access built-in security so they can do their own
maintenance with proper authorization.
Click to expand...

The built-in screens are indeed $#@. However, you can write your own
maintenance screens, & have them do the necessary changes by creating a
temporary "workspace" to perform any actions which the current user might
not normally be allowed to perform.
I now find a need to invoke Access built-in security but
I'd still like to shell the users. I assume I have to
manipulate the mdw file. I tried opening it but it won't
show me any tables, much less how they are structured.
Click to expand...

What do you mean by "shell the users"?

TC
 
So far, I've been able to keep the users out of the
tables and other objects by disallowing Special Keys and
hiding the DB window at Startup. If the Security table
I've built shows you have developer capability, I unhide
the DB window. Needless to say, this capability is
pretty limited.

When I say "shell the users" I mean I'd like to manage
Access security through my own forms. Since my original
post, I found guidance at the MS Developer site with the
syntax for using DAO/ADO/ADOX to open and manipulate an
Access mdw file. For anyone interested, go to

http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/dndao/html/daotoadoupdate_topic7.asp

I don't know how this will display, but it is all one
line....Eric
 
Back
Top