Error: Unable to Attach LIMSDATA.MDB or its Location May Have Changed

Summary

The information in this article applies to LIMS 1.x and Access 2.0.

During system startup the error message “Unable to attach LIMSDATA.MDB or its location may have changed” is displayed if either the location of LIMSDATA has been changed or the file is corrupt. This article describes how to correct the error condition.

More Information

LIMS includes two distinct Access database files: LIMSCODE.MDB and LIMSDATA.MDB. LIMSCODE is the system’s “front end” containing the forms, reports, and software. LIMSDATA is the “back end” repository for the system’s data.

This architecture allows the back end LIMSDATA to reside either on the same machine as LIMSCODE in a standalone configuration or on a shared file server in a multiuser environment.

Each time LIMS is started, the initialization software in LIMSCODE attempts to reestablish a connection to (i.e. reattach) LIMSDATA. If the connection fails, the message “Unable to attach LIMSDATA.MDB or its location may have changed” is displayed. This condition is the result of either an Access error when opening LIMSDATA or moving LIMSDATA to a new drive or directory. The information below offers solutions to either problem.

LIMSDATA Moved

If LIMSDATA has been moved to a new drive or directory perform the following steps:

1. Ensure that the drive/directory is accessible and not read or write-protected.
2. Verify that the “DataDatabase” parameter in the [LIMS Options] section of file LIMS.INI reflects the proper path to LIMSDATA
3. Start the LIMS logging on as LIMSAdmin.

Error Opening LIMSDATA

If LIMSDATA has not recently been moved, exit LIMS at all workstations and attempt to correct the problem following each step below. After each step is successfully completed, attempt to start LIMS. If the error message persists, move on to the next step.

1. Perform a database Repair on LIMSDATA logging on as a member of the Admins group.
2. Perform a database Compact on LIMSDATA logging on as a member of the Admins group.
3. Delete file LIMSDATA.LDB located in the same directory as LIMSDATA.MDB.
4. Use the Access 2.0 Workgroup Administrator utility to join the SYSTEM.MDA workgroup located in the same directory as LIMSDATA.MDB. Now start a full copy of Access 2.0 logging on as a member of the Admins group and attempt to open LIMSDATA.MDB exclusively. Use the error message provided by Access to troubleshoot the problem.

If the previous steps have all failed and you are running In a multiuser environment, copy LIMSDATA.MDB to the workstation’s disk and repeat step #2 using the local copy of LIMSDATA. If the database is successfully compacted, copy it back to the shared directory.