"Jake" <(E-Mail Removed)> wrote in message
news:wLRTa.3684$(E-Mail Removed)...
> I have a client who can no longer use their Access DB. The forms are
> available on their desktop, but when they try to update the database they
> receive a message that reads run time error 3044 and identifies an invalid
> path. The LAN admin has said this is because the database has been moved
to
> another server and the initial server in the path no longer exists.
OK. Can they open the database frontend? (rather than a shortcut to a
form). If so they can use the linked table manager to refresh the links to
the valid path to the backend.
>
> I have found the database on the network and tried to open it, but receive
> the message: "couldn't find system.mdw. This file is required for
startup".
> Also there is a system.ldb file identifying Access Record-locking
> information and a system.mda Access Add-in file. I can't open these.
What version are you using? system.mda was I believe Access 2.0. Try to
delete the ldb file.
>
> I tried to create a path on the network the same as the old path, but this
> was unsuccessful. I also thought using Access from another user would
> activate the default system.mdw file and allow logon as Admin. Didn't
> work.
Well it shouldn't if it was secured properly.
The original creator of the database is gone, and any passwords are
> likely gone too. The database contains important information. I've
scanned
> the SECFAQ download, but I must be missing something.
You need to open the database (frontend) where the forms are, and then
refresh the links to the correct backend database location.
--
Joan Wild
Microsoft Access MVP
|