Spontaneous generation of password control in Access

[Vince]

We are using a product called PES. It is Visual Basic over
Access and is manufactured by EDS. Since the database is
open to us we had created some custom reports and had bulk
loaded it. All was well and we have been using it in
production for several weeks.
This Monday, a user contacted me reporting that they could
no longer use the reports since they didn't have the
password. I checked and access to the database is now
password protected. I checked Microsoft and in their tech
bulletins they have published two related articles.

http://support.microsoft.com/default.aspx?scid=kb;en-
us;243895&Product=acc2000

http://support.microsoft.com/default.aspx?scid=kb;en-
us;321905&Product=acc2000



However, one article dosen't offer any resolution, aside
from "don't do this" and the other offers a solution which
simply does not work. The help desk for the manufacturer
won't support us since "we directly accessed the Access
database". Basically it looks like a corruption problem.
There is a repair tool in the application, but it states
that all users need to be off before using it and of
course all users are off the application. We've re-booted
the server in an effort to clear the lock but to no avail.
Any suggestions you may have would be greatly appreciated.

 

[Cheryl Fischer]

Vince,

To clear a resistant LDB file from the server if a bounce of the server
won't do it, try this:

On the server, open a DOS window and navigate to the folder where the
resistant LDB file is located. Type:

net file Then, press Enter

You should see a listing of all open files, each of which will have a number
(probably 6-digit) assigned to it. In the listing, you should also see the
login id of the user that opened the file. Write down the numbers
associated with each of the ldb files you need to delete.

Then, Type:

net file 987654 /delete

where 987654 is the number associated with an ldb file to be deleted.


Don't know what to tell you regarding the password issue; just continue
monitoring this thread for additional responses.

 

[Joan Wild]

That first article is correct - 'don't do that'. If it had been opened in
Word, then it likely is toast. Your only option is to go to backup.

 

[TC]

Does it ask for a username >and< password, or just a password?

TC