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

[Barmaley]

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

 

[Scott McDaniel]

Using OS or Domain security, you could restrict which users had access to
the Folder and/or File. You couldn't control object permissions in this
method, at least not by using the builtin methods.

 

[Douglas J. Steele]

It's not possible (other than as Scott suggested)

 

[Paul Overway]

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.

 

[Barmaley]

I appretiate your answers guys.
That saved me a lot of time browsing Internet for answers

 

[Barmaley]

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

 

[Jeff Conrad]

in message:

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

Four possibilities come to mind:

1. There may be coding errors in your database. The database cannot be converted
to an MDE file if there are any coding errors. Open any code module and, from the
VBA menu, select Debug, then Compile. If there are any errors, you will see an error
message and the problem line of code will be highlighted. You will need to correct
any problems the compiler finds. Continue compiling until the compile process
completes with no error messages at all. Then try making an MDE file from the database.
Always keep lots of backup copies of the original MDB file.

2. If you are using Access 2002 or 2003, the default database format is Access 2000
unless you have changed this. Unfortunately, if you use the Access 2000 database format
in Access 2002 or 2003, you cannot create an MDE. You may only create an MDE
of an Access 2000-format database using Access 2000. So to make a 2002 MDE file,
you must convert it to 2002 format and use 2002 to make the MDE file. The same is
true for 2003: you need to convert the file to 2003 format and use 2003 to make an
MDE in 2003 format.

3. See this link for another possibility:
ACC2002: Error Message: "Microsoft Access Was Unable to Create an MDE Database"
http://support.microsoft.com/?id=289686

4. Using methods of the DbEngine object without explicitly providing the DbEngine qualifier.
For example: OpenDatabase(...) instead of DbEngine.OpenDatabase(...). This can lead
to strange DAO licencing & other errors, including the inability to create an MDE.
(From a post by TC)

Here is some more info which may help:
Check the "Can't make an MDE!" checklist on the following Web page to help
you determine why you can't create the MDE database:

http://www.Access.QBuilt.com/html/conversion.html

 

[Barmaley]

Hey guys, I am amazed how quickly I received responses.

Thanks a big bunch

 

[Jeff Conrad]

in message:

Hey guys, I am amazed how quickly I received responses.

It does not always happen that way though.
Sometimes it is just a matter of being in the right place at the right time.

Thanks a big bunch

You're welcome, glad we could help.
Good luck with your project.