THIS MANUAL COVERS BOTH LASS 8-11 AND LASS 11-15 EDITIONS, THEREFORE SCREEN PICTURES MAY DIFFER SLIGHTLY FROM WHAT YOU SEE.
At this stage of the installation process for LASS for Networks, it is assumed that you already have an instance of Microsoft SQL Server available to host the database used by LASS. This database will henceforth be called the Lucid database. The database for LASS is installed to a folder just off the application folder root (LASS 8-11 Network or LASS 11-15 Network).
LASS and its database will be on different computers?
If your SQL Server is on a different machine it is advised that you physically move the Lucid database from this server (application) to the other server (SQL Server). This is because SQL Server does not attach databases from different machines as for security reasons it doesn’t work with networked drives, preferring local fixed hard drives.
At the end of this Guide you will find an Appendix which tells you how to move the Lucid database from the server where the application is installed to the server where SQL Server (which will host the Lucid database) is installed.
This is a thin client application, therefore you only install the LASS application once, onto a server, preferably the same one where the SQL Server database engine is.
Multiple workstations (clients) will run the LASS application using a shortcut to the main LASS Tests .exe file on a share on the server. You need to create both the shortcut and the share. There are either one or two small software installs required on each client, missing these out will result in problems running the LASS software. Please see the next guide (GUIDE 3) which tells you how to set up each client machine to run LASS.
The main reports and administration application for LASS has the filename:
LJUNAv603.exe (LASS 8-11)
LSECAv603.exe (LASS 11-15)
This filename was adopted with the previous major edition 6.03-N and has deliberately not been changed even though the edition has since been updated to 6.05-N. Please be aware of this fact as it is not a typing error!