ECM version, OpenLab ChemStation C.01.06


I am working with OL-ChemStation, C.01.06 coupled with ECM Client/Server Version A02.01 (13.3).

I have question to the version number of the result set loaded from ECM (ECM à Load Data from the drop-down list of ChemSation).

When the data was loaded and automatically printed out by sequence (Sequence à View Summary Report File), the version number displayed on the report was not the same one as the loaded ECM Version. It was one version lower with a remark „modified after loading“ within the brackets. It was not true as no data modification was done after loading.

Pls find the attached file for visibility.

The same output was provided when the data set was loaded to the ChemStation, reprocessed and printed out.

How can I get the same version number as that from ECM displayed on the IR report with no remark?

Automatic reprocessing the complete data by sequence is mandatory for the statistic calculation.

Pls advise, thank you


mr. hbar

  • Hi mr. hbar,

    it looks when automatic reprocessing is done (and print report) there is a new revision of result set saved after printing. If this is a "repeatable bug" you can workaround it to customize "ECM version" parameter in Value under "fx" button simply add bracket =Val(ECM_VERSION)+1 

    * change ECM_VERSION to the real name of variable




  • Hello,


    This might work if you are always reprocessing the latest version of the data. The problem is Chemstation does not know anything about the ECM versions of a dataset, except the version of the data set when you last saved or downloaded it from ECM. This means if you have 10 versions of a dataset in ECM and you load back version 5 to reprocess it for some reason when it is uploaded to ECM it will be version 11 but the printouts save with version 11 will have version 5  modified after loading. If you had C.01.07 or higher you could use IR reports in the review mode to printout reports with the current ECM version.


    Marty Adams

  • Thank you Marty and Majkee

    we need to find internal solution to avoid compliance issues which may come up due to the bug of ECM versioning




Reply Children
No Data
Was this helpful?