Access 2003 and Access 2000

R

RT

I have a database that I have secured following Joan Wild's step by step
instructions. After the DB was secured, I then opened Access 2003 (without
opening a database) and rejoined the default workgroup system.mdw.

If I open the secured database is Access 2003, it asks for a password and
seems OK. But I can still open the database if I use Access 2000. I
figured I left out a step or something so I scrapped the whole thing and
started over. The same thing happened again. The database is secured in
Access 2003, but I can still open it without any security if I use Access
2000. I've had both versions installed on my PC for a few years but this
is the DB I have secured using 2003.

The users group has no permissions. The admin user has been removed from
the Admins group and is only in the users group.

What's happening?
 
J

Joan Wild

RT said:
I have a database that I have secured following Joan Wild's step by step
instructions. After the DB was secured, I then opened Access 2003 (without
opening a database) and rejoined the default workgroup system.mdw.

If I open the secured database is Access 2003, it asks for a password and
seems OK. But I can still open the database if I use Access 2000. I
figured I left out a step or something so I scrapped the whole thing and
started over. The same thing happened again. The database is secured in
Access 2003, but I can still open it without any security if I use Access
2000. I've had both versions installed on my PC for a few years but this
is the DB I have secured using 2003.

The users group has no permissions. The admin user has been removed from
the Admins group and is only in the users group.

What's happening?

You missed a step. Are you using the security wizard or doing it manually?
Who is the owner of the database object (and all the other objects for that
matter)?
 
R

RT

I followed your steps (1 to 15, then from 22 to 32. When I got to step 7,
(the user that will own all objects) I created a new user that I wanted to
own the objects and added that user to the Admins group. It isn't myself,
it's another name. On my PC, I don't log on to Windows XP (I'm the only
user here), so I didn't think it would matter and I created the user that
will be using the DB as owner and gave her a password. This user owns all
of the objects.

Then I gave the admin user a password (after I removed this user from the
Admins group).

I used the "user level security wizard" in step 14. I know I must have
skipped something but for the life of me, I can't see it. If I join the new
secure workgroup, I can't open it without a password. If I join the default
workgroup (system.mdw), I can open it without any password.

I am going to start over. Is there anything I should do different. Not use
the security wizard?

Thanks for answering.
 
J

Joan Wild

It is important that you follow each step, in order. What you outlined
below is not the correct order.

You don't mention the version you are using to secure it with (2000 or
2003).

If it's 2000, don't use the wizard. If you are using 2003, you can use the
wizard (but use it from the start, not half way through).


--
Joan Wild
Microsoft Access MVP
RT said:
I followed your steps (1 to 15, then from 22 to 32. When I got to step 7,
(the user that will own all objects) I created a new user that I wanted to
own the objects and added that user to the Admins group. It isn't myself,
it's another name. On my PC, I don't log on to Windows XP (I'm the only
user here), so I didn't think it would matter and I created the user that
will be using the DB as owner and gave her a password. This user owns all
of the objects.

Then I gave the admin user a password (after I removed this user from the
Admins group).

I used the "user level security wizard" in step 14. I know I must have
skipped something but for the life of me, I can't see it. If I join the
new secure workgroup, I can't open it without a password. If I join the
default workgroup (system.mdw), I can open it without any password.

I am going to start over. Is there anything I should do different. Not
use the security wizard?

Thanks for answering.
 
R

RT

I'm securing it 2003. I'm not sure if I understand about the half-way
through part. I followed your steps 1 to 15 then it said to proceed to step
22. (Depending on who I want to own the DB etc). In steps 1 to 15, I
create the workgroup first without opening the DB. If I go to step 16 to
begin, I'm instructed to open the unsecured DB first then create the
workgroup. I thought to create a user that will use the DB on a daily basis
and have full/all permissions. Should I not do this?




Joan Wild said:
It is important that you follow each step, in order. What you outlined
below is not the correct order.

You don't mention the version you are using to secure it with (2000 or
2003).

If it's 2000, don't use the wizard. If you are using 2003, you can use
the wizard (but use it from the start, not half way through).
 
R

RT

Joan,
I redid your steps. It seems to have worked this time.

I wish I knew what I missed the first time but thanks so much for the help.


Joan Wild said:
It is important that you follow each step, in order. What you outlined
below is not the correct order.

You don't mention the version you are using to secure it with (2000 or
2003).

If it's 2000, don't use the wizard. If you are using 2003, you can use
the wizard (but use it from the start, not half way through).
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top