Re: What is wrong or missing if I can't modefy an exisiting workgroup?

anonymous_at_discussions.microsoft.com
Date: 08/16/04 

Date: Sun, 15 Aug 2004 22:30:28 -0700

Joan,

thanks for your reply.
In my email I refer to instructions from your webpage.
I don't know hoe many times I have gone over and through
them. They appears straight forward and logical.

I followed the instruction by the book in on my home
network. It worked Ok.

At work:
1)I wasn't able to remove admins group form User Admin.
2)I could not modify the newly created .mdw file!!

In the meantime I found out that some people have pampered
with the system.mdw, whereas I was assumming that it was
in its original stage. Could that have an impacked??
a)I replaced the system.mdw with a new installation file.

I managed to get to question 15. Open the jet unsecured
database and managed to modify the existing newsystem.dmw.
Printed the report. Not shortcut was created. ( I created
one)+ .bak file + snapshotviewer.

Owner of the objects was administrator. Jet, I found admin
rights where set to read only!!!!, hence I could not
modify any design neither could I change access rights...

Is this because the objects + scurity setting, the db and
system.mdw under which the database was developed, were
inherited??

I than loged on as admin again and reset the admin rights
to reflect the default.

Now during my session I could not open the database with
out been Prompeted for a password. However I could open
strait awag the db form any other computer on the net work.

Allthough I found an application that had security
implemented as It shoudl work and it works oK.
I compared both setting. They are not in any way different
except the firstone provide security and the 2nd dones't

At one stage I created a new database. Implemented scurity
and imported all objects, with little to none success. All
forms were not importable. Error message state: Can't copy
now... is currently open by someone else exclusively??
Jet, I was the only one who had 1 application open!

Would you have any other suggestion what to try.

any hints are much appreciated.

Norman F
>-----Original Message-----
>Normanf wrote:
>> Hi there,
>>
>> What is wrong or missing if I can't modefy an exisiting
workgroup????
>> I followed the securities manual instruction step 1 to
15 whereas in
>> the next step I would like to modefy the existing
workgroup, but the
>> check box is greyed out.
>
>I'm not sure what you mean; the security FAQ lists 10
steps.
>
>To modify the existing workgroup, you can create a
desktop shortcut with the
>following in the target.
>"path to msaccess.exe" "path to secure mdb" /wrkgrp "path
to secure.mdw"
>
>Once you log in, you will be joined to the secure
workgroup. You can go to
>Tools, Security, User and Group Accounts (to modify
groups,users,
>membership) or to User and Group Permissions, to modify
the permissions on
>the database objects.
>
>
>--
>Joan Wild
>Microsoft Access MVP
>
>
>.
>

Relevant Pages

  • Re: Sorting out security
    ... > MS Access security. ... > created a new workgroup, added a password for the Admin role, added ... > remote logins to a secured database. ... The location of the current workgroup file is recorded in the ...
    (microsoft.public.access.security)
  • Sorting out security
    ... MS Access security. ... created a new workgroup, added a password for the Admin role, added groups, ... user IDs and passwords for users and allocated permissions on the ... remote logins to a secured database. ...
    (microsoft.public.access.security)
  • Re: Problems setting up access security
    ... So, for some reason, it seems that Access security does not work when Access ... try to go directly into the database, they have to use the shortcut and log ... "Joan Wild" wrote: ... The Admin user still owns the database object. ...
    (microsoft.public.access.security)
  • Re: Sorting out security
    ... There is a link to it on the Security page of my website. ... > files and remote logins to a secured database. ... different name for the secure workgroup file. ... If the Admin user has no password then every user is ...
    (microsoft.public.access.security)
  • RE: How to remove user level security
    ... It sounds like you did not secure your database but you just forget what ... the passwords are for the Admin account and the account that has Admins ... Reopen Microsoft Access and try opening one of your databases. ... The security wizard creates a ...
    (microsoft.public.access.security)