ACCESS FEED: [MS_AccessPros] Re: Single user to multi user

Jumat, 16 Agustus 2013

[MS_AccessPros] Re: Single user to multi user

Hi Liz

Most of my applications have user administrators so I don't have to mess with permissions. All I do is make adjustments when design changes are made. I also include a permissions "rank" in the user group table. Initially, there are groups ranked from 10 to 100 incremented by 10. That leaves me enough gaps to add levels if need be. And I'm always the only one with a 100 rank.

I even go so far as to write code so I can spoof as another user to test what a given rank will be able to do. That comes in handy during testing.

Bill

--- In MS_Access_Professionals@yahoogroups.com, Liz Ravenwood <liz_ravenwood@...> wrote:
>
> I'm enjoying having the users police themselves. I use the getlogin code I found to get the network login id and then based on that, they can add others to their secure group which in turn can set controls to visible, disabled, accessible...
>
> Respectfully,
> Liz Ravenwood
> Programmer / Analyst
> B/E Aerospace | Super First Class Environments
>
> 1851 S Pantano Road | Tucson, Arizona 85710
> Office +1.520.239.4808 |
> beaerospace.com
> Passion to Innovate. Power to Deliver
>
> -----Original Message-----
> From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Bill Mosca
> Sent: Friday, August 16, 2013 8:52 AM
> To: MS_Access_Professionals@yahoogroups.com
> Subject: [MS_AccessPros] Re: Single user to multi user
>
> Phil
>
> I find it easier to apply the security first and then split. That way you are sure to have the security on the tables set at the same time as the other objects.
>
> By the bye, you might want to consider going with a do-it-yourself security since the new ACCDB file format does not allow User Level Security. Scott Diamond wrote a couple of good blogs explaining how to do this. You can read them at:
> www.accesssecurityblog.com/post/Securing-Access-databases-using-Active-Directory.aspx
> www.accesssecurityblog.com/post/2011/04/02/Login-Security-using-Access-VBA.aspx
>
> Regards,
> Bill Mosca, Founder - MS_Access_Professionals http://www.thatlldoit.com Microsoft Office Access MVP https://mvp.support.microsoft.com/profile=C4D9F5E7-BB03-4291-B816-64270730881E
> My nothing-to-do-with-Access blog
> http://wrmosca.wordpress.com
>
>
>
> --- In MS_Access_Professionals@yahoogroups.com, "pdk444444" <pdk444444@> wrote:
> >
> > Hi Guys
> >
> > I have a single user database that I want to develop into a multiuser
> > and split at the same time
> >
> > Is it best to split first and then apply the user security (it is mdb) or vice versa or does it make no difference?
> >
> > cheers
> >
> > Phil
> >
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>
>
>
> This email (and all attachments) is for the sole use of the intended recipient(s) and may contain privileged and/or proprietary information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
>