error messages, "joining" the .mdb file, user password

  • Thread starter Thread starter Tammy
  • Start date Start date
T

Tammy

Okay, this is my first time using the security wizard. I
used it, set up the user files, passwords - etc. Anyway,
I was concerned about not having the proper rights as the
owner and tried to check it - in the process, I "joined"
with the system.mdb user group file - or something. Can
I retract this?? What will this do?

Also, I have one user where I apparently mistyped his
password. I have gone in to the user security menu and
tried to "clear password" - but when I try to change it,
the system doesn't accept the old password. I thought I
would delete the user and recreate him - but didn't know
if that would cause errors. Any suggestions?

Now, for the third and final (I hope!) question - certain
users cannot access certain forms or menus. When they
try, I would like to replace the system error message
with my own. Also, there is one menu selection on the
main menu that a user without permission cannot access -
when the user tries, I would like focus to go back to the
main menu - at this point it closes the main menu and
a "blank" Access window is left. I need to change that!

Thanks for any suggestions!
 
Tammy said:
Okay, this is my first time using the security wizard. I
used it, set up the user files, passwords - etc. Anyway,
I was concerned about not having the proper rights as the
owner and tried to check it - in the process, I "joined"
with the system.mdb user group file - or something. Can
I retract this?? What will this do?

I think you mean that you joined system.mdw. Once you did, you should try
to open your secure mdb - you shouldn't be able to if you implemented
security properly. Once tested, leave your computer joined to system.mdw
and create a desktop shortcut (if the wizard didn't) to open your secure
mdb, that points to the correct mdw. It's target would look like
"path to msaccess.exe" "path to mdb" /wrkgrp "path to secure.mdw"
Also, I have one user where I apparently mistyped his
password. I have gone in to the user security menu and
tried to "clear password" - but when I try to change it,
the system doesn't accept the old password. I thought I
would delete the user and recreate him - but didn't know
if that would cause errors. Any suggestions?

You may be confusing a PID with a password. Usually (it depends on version)
when you create users, you enter a PID (this is not a password), and their
initial password is blank. Try logging in with a blank password.
Now, for the third and final (I hope!) question - certain
users cannot access certain forms or menus. When they
try, I would like to replace the system error message
with my own.

Instead of doing that, I would hide forms/menus from them in the first
place.

Also, there is one menu selection on the
main menu that a user without permission cannot access -
when the user tries, I would like focus to go back to the
main menu - at this point it closes the main menu and
a "blank" Access window is left. I need to change that!

Again, don't present it to them in the first place. There is code in the
security FAQ you can use to determine if a user is a member of a group. You
can hide things based on this.
 
I had the shortcut made originally. When I click on that
one, I can open it without error. I believe when I go
through the menu selection I do (not sure on that, have
to double check!)

I will try out the blank and see what happens, it could
have been that. But I used the wizard and created the
users/passwords(?). The passwords I am using for
everyone else worked.

Thanks for all the suggestions! I'll work with them and
see what happens!
 
OK, well, I have checked both things. I can get into the
database, both ways and I was able to log in as that
individual with a blank password - THANKS! On the
system.mdw thing, is there anything else I need to check
or do to insure things are okay??

THANKS again!
 
Tammy said:
OK, well, I have checked both things. I can get into the
database, both ways and I was able to log in as that
individual with a blank password - THANKS! On the
system.mdw thing, is there anything else I need to check
or do to insure things are okay??

I'm unclear here. You should NOT be able to open your database just by
double clicking it in Windows Explorer. If you can then it isn't secure.
 
Well, I do not get any error messages - if that's what
you mean. I get the login screen. I can get in
as "owner". I am guessing that is what you are referring
to - and if this was working or done correctly I wouldn't
be able to get to the login screen - right?!

On that note, when you say I should just not make the
menu item available; I should just check the user group -
how do I do this?? Is there a property? Sorry for my
ignorance! To be honest, I haven't checked the help
screen for that - sorry, I don't normally do that! I
guess I thought I would throw it out there since I'm on
here!

Thanks again!
 
Hi Tammy,

Tammy said:
Well, I do not get any error messages - if that's what
you mean. I get the login screen. I can get in
as "owner". I am guessing that is what you are referring
to - and if this was working or done correctly I wouldn't
be able to get to the login screen - right?!

What I mean is:
Join standard system.mdw workgroup (using workgroup administrator)
Open Windows Explorer
Double-click your mdb file
It should not even open (no dialog, no login, nothing - you should get a
message saying you don't have permission to use xxxx.mdb)
On that note, when you say I should just not make the
menu item available; I should just check the user group -
how do I do this?? Is there a property? Sorry for my
ignorance! To be honest, I haven't checked the help
screen for that - sorry, I don't normally do that! I
guess I thought I would throw it out there since I'm on
here!

The security FAQ (I assume you have it, if not it's at
http://support.microsoft.com/?kbid=207793
contains sample code you can use to determine if a user is a member of a
group.
 
Tammy said:
I am not sure why, but I have done this and I am still
able to getr in...

If you are able to get in using the standard system.mdw then it wasn't
secured properly. If you haven't got it, download and study the security
FAQ at
http://support.microsoft.com/?kbid=207793
Follow every step outlined.

I would guess that the Admin user still owns some objects, or the Users
group still has permission to open/run the database object. Double check
both these.

I have even looked at
the "properties" which gave a path to the system.mdw?!

Post here exactly what is in the target line of the properties. There
should be more than a path to the mdw.
 
Back
Top