Lost logon

[Guest]

The logon screen to my network-resident form/database fails to display. Although I am the Admin, Creator, etc., the db doesn't know it because there is no logon screen. No other users have the logon either. Any way to recover it?

 

[Joan Wild]

No logon would happen if the password was cleared for the 'Admin' user. Or
it's possible you are getting in using the standard system.mdw.

If you secured it properly, the latter shouldn't work. If you are not able
to get in, then you may just not be using your secure mdw. You can use a
desktop shortcut with a target like
"path to msaccess.exe" "path to mdb" /wrkgrp "path to secure mdw"


--
Joan Wild
Microsoft Access MVP

The logon screen to my network-resident form/database fails to display.

Although I am the Admin, Creator, etc., the db doesn't know it because there
is no logon screen. No other users have the logon either. Any way to
recover it?

 

[Joan Wild]

You can open Access and go to tools, security, workgroup administrator. Set
your secure mdw as the default one to use.

Create a new database - just to ensure that the secure mdw is in use. You
won't get a login prompt, but you will be logging in as 'Admin' with no
password. Next go to the Tools, security, accounts menu. Click on Change
password, and set a password for the Admin user.

That should fix it. You will want to use the workgroup administrator to
rejoin the default system.mdw workgroup.

--
Joan Wild
Microsoft Access MVP

Everyone is able to 'get in' to the location but, without the logon

screen, no one has any rights, including me. Any way to re-enable the logon
screen?

 

[Guest]

That did the trick. Many thanks. Now back to the first problem of multiple simultaneous access to the db. Can you comment on this statement from another thread

"The problem is that you apparently have to give full read-write WINDOW
permissions to the folder where the database is located for a user to eve
open it, else you get an "already in use" error. Problem is, in doing this
you leave open the risk that someone could outright delete the files.â€

Since all was working fine until a certain point at which, I surmise, a change to the network took place, do you give any weight to the statement as being contributory to my problem? IT has denied any change took place - but I see Novell Network on my computer when I didn't see it before.

 

[Joan Wild]

I'm confused. What does this have to do with your original question?

The only way that the Admin password was changed to blank, was that someone
(a member of the Admins group in the Access mdw file) went to Tools,
security, Accounts, and clicked on Clear Password - perhaps by accident. In
other words, Admin is the first user in the list. They may have forgotten
to select the correct username, before hitting Clear Password, and as such
cleared the password for Admin.

As far as concerns about giving users full permissions to the folder. Yes
that is required. You can hide the folder so it isn't so easy for them to
get to and delete files (use \\server\share$ rather than \\server\share).
You can also deny delete permission on the mdb file, however when you
compact you have to remember to reset the deny permission. Of course,
you'll have backups should someone delete it.

Also for multiple users, you should split the mdb and put just the backend
on the server. Give each user a copy of the frontend on their local
machine.

--
Joan Wild
Microsoft Access MVP

That did the trick. Many thanks. Now back to the first problem of

multiple simultaneous access to the db. Can you comment on this statement
from another thread:

"The problem is that you apparently have to give full read-write WINDOWS
permissions to the folder where the database is located for a user to even
open it, else you get an "already in use" error. Problem is, in doing this,
you leave open the risk that someone could outright delete the files."

Since all was working fine until a certain point at which, I surmise, a

change to the network took place, do you give any weight to the statement as
being contributory to my problem? IT has denied any change took place - but
I see Novell Network on my computer when I didn't see it before.

 

[Guest]

Sorry for the confusion. It was during my attempts to fix the first problem that I caused the second problem. I thought that turning off the password would free up the database to all the users. Very wrong idea. I can see (now) that the separation of the front/back end is necessary and will pursue that. Thanks for your views on the network issue. I will explore that as well.