Re: Always asked to login, and I can't!

Hi, David.

Every time I open a database (old MDB type) or try to create a new
database
(new type), I get asked for a username and password.

You are currently joined to a workgroup where the default Admin user has a
password set. This is known as a "secure" workgroup.

The default username given is "Admin" and I try to use this with a blank
password.

The default Admin user most definitely has a password, so you must supply it
if you want to open or create a database file.

I have recently renamed the Windows user that I am using to run Access,
but
surely that doesn't make a difference?

No. If one joins a workgroup where the default Admin user has a password
set, then this will ensure that the user gets prompted for the User ID and
password when opening or creating a database file.

Any ideas on what else I can try?

Find a workgroup file that isn't secured and join it, or else remove the
password from the default Admin user of the current workgroup. The default
workgroup, System.MDW, is unsecured, so I'd recommend finding and joining
that one unless, of course, you intentionally secured it by assigning a
password to the default Admin user in the default workgroup on your own
workstation.

For the recommended method of opening databases when some databases are
secured and some are not, please see the tip, "How to open databases and
only be prompted for User ID and password for the secure databases," on the
following Web page:

http://www.access.qbuilt.com/html/security.html

Of course, you have Access 2007, so use the built-in Workgroup
Administrator, not the separate WRKGADM.Exe file, to join another workgroup.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.


.

Relevant Pages

  • Re: Access Security not secure
    ... You should secure it manually. ... > In your test with using a new workgroup and running the> wizard it was in access2000 then again in access2002 ... >>> to work well until I try to access the database on the ... >>>>> I created the Administrator and added him to the> admin ...
    (microsoft.public.access.security)
  • Re: Is someone hacking into our database?
    ... is only about 90-100 mb in size) because the database goes screwy and begins ... but that I know of no way to keep it secure (due to the ... I changed to that workgroup, ... is a member of the Admins Group in system.mdw. ...
    (microsoft.public.access.security)
  • Re: Baffled By Security Wizard
    ... I did in fact add the Group to my secure workgroup. ... I'm not clear on why importing the ... objects into a new database was critical. ...
    (microsoft.public.access.security)
  • Re: Sticking with a defined Workgroup.
    ... workgroup file called system.mdw. ... So when you 'join' your secure mdw on the server, it is now the default mdw ... My trouble is that when I distributed my secure database by putting ...
    (microsoft.public.access.security)
  • Re: Security - Security & User Accounts
    ... You are currently joined to the workgroup file you secured ... password set so Access silently logs you into the database ... and then how can I set up secure logins for ...
    (microsoft.public.access.formscoding)
Loading