I just upgraded from A2000 to A2003. Playing with passwords, I added one to a
database.

Then, I opened it from the File Open menu, clicking on Open Exclusive. When I
try to unset the password, it says I need to open the database for exclusive
use, and gives the exact procedure I followed.

Did I miss something?

Thanks.

I suspect that the ldb file wasn't deleted the last time that it was open.
Close the database, make sure no one else has it open, then go to the folder
that the database is in and look for an *.ldb file with the same name as the
*.mdb file. If the ldb file is there, delete it and try again.

--
Wayne Morgan
Microsoft Access MVP


"OceansideDJ" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I just upgraded from A2000 to A2003. Playing with passwords, I added one
to a
> database.
>
> Then, I opened it from the File Open menu, clicking on Open Exclusive.
When I
> try to unset the password, it says I need to open the database for
exclusive
> use, and gives the exact procedure I followed.
>
> Did I miss something?
>
> Thanks.

Wayne,
Explorer shows no Idb file left over.

I did fix another problem of Linked Table Manager showing a blank table list.
Access was still reading the old accwiz.dll. I fixed that per Microsoft's
known bug fix.

Could the password problem be similar? I assume it would be safer not to use
any passwording until this is resolved.

Mike

It should be LDB not IDB. Yes, I would leave the password off of anything
other than test database files until you know that you have it working.

If the database will let you in, just not remove the password, try creating
a new database and import the object from the troublesome one.

--
Wayne Morgan
Microsoft Access MVP


"OceansideDJ" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Wayne,
> Explorer shows no Idb file left over.
>
> I did fix another problem of Linked Table Manager showing a blank table
list.
> Access was still reading the old accwiz.dll. I fixed that per Microsoft's
> known bug fix.
>
> Could the password problem be similar? I assume it would be safer not to
use
> any passwording until this is resolved.
>
> Mike