Re: unknown database owner

In the second, it isn't asking for a password because the password has been
cleared for the 'Admin' user. Set a password for this user and you'll get
the login dialog.

--
Joan Wild
Microsoft Access MVP
"Eugen S. Teodor" <teo@xxxxxxx> wrote in message
news:4FE14A6D-15BA-4355-B541-54839673C376@xxxxxxxxxxxxxxxx
You should be right. Normally... But... My message intended to be short,
but
ended to be confused. There are two different situations. I used, over
time,
two different system files, and when I saw that the database does't work,
I
tried them both. In the first case, the "owner is unknown" (you described
already the situation), but in the second (the most interesting) is that I
already described: it doesn't ask for password, the access to data is
forbiden, the owner is known (myself), but it will never know, because
does
not ask for... I hope this time I was clearer.
--
esteo


"Rick Brandt" wrote:

Eugen S. Teodor wrote:
I am not an expert or a proffesional in computing, but I am working
with Access and system files from at least 10 years. Along time I was
frecquently in the position to share databases, with end users etc.
But I never saw this: An old database, converted from 97 version to
2000, now to 2003, used at least once per week, suddently stoped to
recognise my as the owner. In fact, it does not ask for a user name
and password anymore.
I want to prevent the standard answer and I am telling you that is
the right system file. What is to do next? The database is rather
large, and when I'm thinking to do it from the scratch...
Sorry for misspelling. That's it. I am not a native...

You are mistaken. If you are not being prompted then either someone has
removed
the password from the Admin user on your workgroup file or (more likely)
it is
NOT the correct workgroup file. And since you can open the file without
logging
in then security was never correct in the first place.

An owner of "unknown" absolutely means that the object was created by an
account
that does not exist in the workgroup file currently in use.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com





.

Relevant Pages

  • RE: Access 97 Security issue Cant make a MDE
    ... "If the database is secured using user-level security, ... logged in as the owner of the database, or at least a member of the Admins ... > the dayabase as a user AND can sign in simply as admin, ... > that the user account has Modify Design or Administer permissions for the ...
    (microsoft.public.access.security)
  • Re: silly question
    ... >have read about problems of the owner of the object, ... >referring that a person who has Admin rights on the Windows operating system ... I have a paper that may help with your understanding how security work ... >If my understanding is correct, I created a database on our server, I'm not ...
    (microsoft.public.access.security)
  • Re: unknown database owner
    ... "Joan Wild" wrote: ... the "owner is unknown" (you described ... An old database, ... Rick Brandt, Microsoft Access MVP ...
    (microsoft.public.access.security)
  • Re: User Level Security Malfunction
    ... The person who logged on to Access when the database was created is the owner. ... If you are listed as the owner, you created the database while logged on as yourself, not as Admin. ... Are you opening the database by way of a shortcut that includes the path to the Security.mdw file, or have you changed the default mdw file on your installation of Access? ...
    (microsoft.public.access.security)
  • Re: RWOP /table permissions question
    ... They aren't in the default admin group. ... Microsoft Access MVP ... can't the users with admin rights still create a new database ... Now base all your SQL statements on these queries rather than ...
    (microsoft.public.access.security)