System

This information in this article applies to LIMS 4.x.

A runtime error may occur in the results entry screens when importing results from Excel. Note that the error may be limited to a specific workstation in a multi-user installation and will only occur with LIMS version 3.3...

Typical LIMS multi-user installations use traditional client/server architecture. That is, the LIMS front end software is installed locally on each LIMS workstation sharing the back end database from a shared folder on a file server. Thi...

This information in this article applies to LIMS 3.x.

This article describes the procedures required to move LimsData, the LIMS back end database, to a new disk drive and/or folder.

Follow the procedures outlined in this article to create your own version of the LIMS software. Use this development version to create and test new bench sheets, reports, and other customizations.

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 e...

During system startup, LIMS checks the compiled state of the system’s Visual Basic for Applications (VBA) project. The VBA project contains all code modules including code behind forms and reports. When the VBA project is not in a compil...

This article describes the nature of the barcodes used within the LIMS software and how similar barcodes can be generated using other Windows programs.

This article outlines the benefits of incorporating a read-only copy of LIMSDATA in a multiuser environment. Instructions to configure a read-only version are also included.

The faster Microsoft Access runs, the faster LIMS runs. Follow the tips in this article to improve overall system performance.