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

If I try to create MDE file and Access returns message: "Mcrosoft Access was
unable to create an MDE database"
Is there some restrictions?


"Paul Overway" <paul@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:OSeInUvNFHA.2468@xxxxxxxxxxxxxxxxxxxxxxx
> 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

  • Re: MDE not possible ?
    ... First compile the MDB and make sure that there are no errors in the code ... before creating the MDE. ... Because of the methode used to compile the database a lot of references ... If your database is in Access 2000 file format (it should say on ...
    (microsoft.public.access.formscoding)
  • Re: Acces VBA Password
    ... > the product, the Make MDE file selection is not enabled on the Tools, ... Web page to help you determine why you can't create the MDE database: ... version of the VBA source code, even if there's a VBA password placed on the ...
    (microsoft.public.access.security)
  • Re: MDE not possible ?
    ... I converted my frontend MDB to the Access 2002-2003 format and tried to ... I get an error that the MDE couldn't be created. ... This error occurse mostly while compiling big databases to a MDE file. ... Because of the methode used to compile the database a lot of references will ...
    (microsoft.public.access.formscoding)
  • Re: Log In
    ... Microsoft Office Access was unable to create an MDE database. ... R_W - read and write permission but cannot delete or modfiy existing reocrds ...
    (microsoft.public.access.security)
  • Re: Log In
    ... Microsoft Access MVP ... Microsoft Office Access was unable to create an MDE database. ... opens the form? ...
    (microsoft.public.access.security)
Quantcast