Re: Replacing Workgroup Security with Domain Groups/Acounts - is it possible

If your sole purpose for implementing workgroup security was to prevent
modifications to forms, a better solution would be to distribute an MDE vs
an MDB. This would eliminate the need for maintaining 2 sets of
usernames/passwords. However, if you have a real need for workgroup
security, i.e., to prevent use of certain functionality, you're stuck with
maintaining both lists. Even if you did need to restrict use of certain
functionality, permissions on your SQL database could serve to limit access
to certain tables, views, etc. and prevent manipulation of the underlying
data...depending on how it was done, your users might see errors if they try
to do something they aren't supposed to do, but you wouldn't have the 2
lists to maintain. However, you'd probably have more error trapping to do.

--
Paul Overway
Logico Solutions
http://www.logico-solutions.com


"Barmaley" <someone@xxxxxxxxxxx> wrote in message
news:d2k3o4$44v$1@xxxxxxxxxxxxxxxxx
> Hi,
>
> I am new to this group, so forgive me if that was answered here
> previously.
>
> Situation as follows:
> We have Database with back end on SQL server and Front end as Access MDB
> with workgroup security setup to restrict editing the forms etc
> We have already setup Domain Groups to give permissions to SQL database
> and
> folders where Front End DB resides.
> But with workgroup security users must remember another set of username
> and
> password, and it is hard to enforce 90 days password change policy.
>
> So my question is:
> Is it possible to do Workgroup type security, but assigned to Domain
> groups
> not local to MDB set of Groups and Users.
> So by putting Users to Domain group will give them all neccessary
> permissions ?
>
> Thanks in Advance
>
>


.

Relevant Pages