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

[Guest]

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.

Now the existing wrokgrou was created in access whereas no database was
selected.

What could I do??
do differently??

Kind regards Norman f

 

[Joan Wild]

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.

 

[Guest]

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

 

[Joan Wild]

Hi Norman

thanks for your reply.
In my email I refer to instructions from your webpage.

Well you either go 1-15, 22 to the end or 16 to the end.

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

So you know it works.

At work:
1)I wasn't able to remove admins group form User Admin.

You can only do this *if* some other user is a member of the Admins group -
someone has to be a member of that group.

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??

Only if they have tampered with the system.mdw on your computer. Tampering
with their own will not have an impact.

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.

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.

That indicates that it isn't secured; either the Users Group has permissions
or the Admin user owns objects.
During the wizard, did you decline to put permissions on the Users Group?

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

Well something is different ;-)

Would you have any other suggestion what to try.

I would suggest that you start over. Go back to the unsecured backup of the
mdb. Delete all the workgroup files you have. Open Access, and it will
create a new system.mdw file. Then start over (starting at step 16)