MultiTrace Database connectivity

From MassFinder

Jump to: navigation, search
MultiTrace 3: Manual

Contents

Result file ID

The result file ID feature is one of the most exciting and efficiency-increasing database-related options of MultiTrace. If you want to start with database features, we strongly recommend to start with the result file ID feature, because it is both relatively easy to set-up and has an excellent return-of-investment with regards to time and efficiency.

MultiTrace stores evaluation results of a sample in result files and keeps the whole history of restuls files in the raw data file folder. If one user prints or closes and re-opens a sample several times or if several users work (intentionally or accidentally) on the same sample, results never overwrite each other and whoever will open a sample again, will have the choice between all saved results files, which clearly shpw a date-time stamp, the user name and information about the evaluation results. This cocnept ensures, that all printed reports will always have a corresponding result file of exactly the same content.

While it is possible to determine the corresponding result file by comparing the date-time stamp and user name, it is much easier to use the result file ID feature described here. If activated, MultiTrace generates a unique result file ID for each saved result file, stores this ID in the result file and prints this ID on all reports both as number and barcode.

Whenever you need to call up this result file, e.g. because a supervisor wants to check or a quality control team wants to peruse the old evaluation, you simply need to strike the "PAUSE" key and to type or scan in the barcode number and MultiTrace will change the active folder to the correct instrument, open the needed references, open the sample raw data file and open the selected result file. If newer result files exist than the called result file, MultiTrace will display a table of all result files, highlight the scanned result file and lets you descide which result file to open.

The result file ID feature is also part of inter-application communications with other software products of Hochmuth Scientific Consulting. For example, the evaluation software Eva 2.x can remotely control MultiTrace to open up a certain result file and jump to a certain parameter and highlight the integral area that gave rise for the numerical result you selected in Eva.

db.ini

[SetResultFile]
SQL=call MultiTrace3_ProcW_SetResultFile (@UserName = '§UserName#',
 @ResultFile = '§ResultFile#', @SampleID = '§SampleID#', @Application =
 '§Application#')
CS=SpechtDB
Field_ResultFileID=ResultFileID
[GetResultFile]
Enabled=1
SQL=call MultiTrace3_ProcR_GetResultFile (@ResFiID = '§ResultFileID#')
CS=SpechtDB
Field_ResultFile=ResultFile
Field_SampleID=SampleID
Field_Application=Application

parameters

  • §ResultFileID# -- long integer, unique, auto-increment
  • §ResultFile# -- varchar -- path and filename of the result file
  • §SampleID# -- varchar -- sampleID (primary LIMS identifier of sample)
  • §UserName# -- varchar -- login name of the Windows user
  • §Application# -- varchar -- 'MultiTrace'

SampleID details

The sample ID details routine queries several LIMS parameters for a given sample: matrix, customer name, customer description, target time, country of origin. If necessary, it will be possible to easily add further parameters to this query.

The parameters are shown in the main view of MultiTrace and can be of interest to the operator.

db.ini

[GetMatrixByAz]
Enabled=1
SQL=call ProcR_MultiGC_getMatrixKunde('§SampleID#')
CS=LIMS
Field_Matrix=Matrix
Field_Customer=Customer
Field_Origin=Origin
Field_Description=Description
Field_TargetTime=TargetTime

parameters

  • §SampleID# -- varchar -- sampleID (primary LIMS identifier of sample)
Personal tools