Do I need desecure the DB before I secure it again?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have one db not properly secured for the user-level security(any user can
open the db using default system.mdw without joining the workgroup), and I
need redo the security procedure. Do I need do anything to de-secure the db
before I start securing it again?

Thanks for your help!
 
=?Utf-8?B?amVzc2ljYQ==?= said:
I have one db not properly secured for the user-level security(any user
can open the db using default system.mdw without joining the
workgroup), and I need redo the security procedure. Do I need do
anything to de-secure the db before I start securing it again?
Click to expand...

No, you should be fine working with the one you have. If you're at all
concerned then you could always export all of the objects to a new blank
database file joined to system.mdw (assuming it hasn't been modified).

Regards,
Keith.
www.keithwilby.com
 
Hello White,

I got messages when I tried to "Import" the OLD SECURED (Please note
this)database on the step 15(secure it manually rather than using Security
Wizard) of your article "Access 97/2000 security step by step" posted on

http://www.jmwild.com/security97.htm

and the error message is saying:" You do not have the necessary permissions
to use db1.mdb object, have your system admin or the person who create this
object establish appropriate the permission for you". I have tried to remove
the Admin password for old .mdb and put Admin user back to Admins group using
the previous .mdw workgroup file but it did not work. I think because I am
using the new created .mdw and another user other than Admin to login and
trying to import the secured db. I am confusing for the .mdws. So can you
tell me what extra step should I do to successfully import the previous
secured db?
Or how can I export the previous secured db ?(looks like I can only export
one object a time, Oh there are so many objects in my .mdb)

Any suggestions or comments? Appreciated!

Thanks!
 
=?Utf-8?B?amVzc2ljYQ==?= said:
I got messages when I tried to "Import" the OLD SECURED (Please note
this)database on the step 15(secure it manually rather than using
Security Wizard) of your article "Access 97/2000 security step by step"
posted on

http://www.jmwild.com/security97.htm
Click to expand...

Have you tried granting full permissions to all objects to the 'user'
account?

Regards,
Keith.
 
No, I did not. Do you indicate that I did not de-secure the database
properly? (grant full permissions to the users group and Admin user account,
put the admin back into admins group and remove the password for admin)

I tried another way, because my preivous secured db having problems with
Admin user(any network user can open it without using the right .mdw but
using system.mdw). So I import the previous "Secured?" db using Admin first,
then import the db again using the account(jessica) who is in the admins
group now. And I checked the "Users and Group Permissions", the owener is
jessica for all the db objects, and "users" group have all the full
permissions on the db objects(only except "database" object, none permission
is granted, why?) I think this time Access is considering imported objects to
be "new" and losing the permissions info that was stored in the source
database.

Because this is second(maybe third) time to secure the db again and I want
this time to do it properly so that I can starting using it. I have to be
very cautious and please give me a shot if there is anything wrong with my
previous step rather than give full permissions to "Users" group account
before importing the db, thanks!
 
Back
Top