by
jwmol » Tue Jul 25, 2006 9:12 pm
Hi Slaven,
I understand you want to avoid having to buy the automation license.
A custom parameter script is able to call an external DLL.
However what you need is a "trick" to let the continue/repeat run decission take its action. There is only one way that I know (other than the automation interface) and that is what I tried to explain by using the system suitability functionality in a sequence.
1. Your DLL will tell the customer parameter to continue or to repeat. Let's say that continue=1 and repeat=0 as a return value of the custom parameter.
2. In the System Suitability conditions of the method it is specified that when your custom paramter <1 that the system suitability fails.
3. In the sequence you specify one or more system suitbalilty runs. In the action field of each run you specify that when system suitability fails the entry is re-run until it succeeds.
There is a substantial difference between a custom parameter (even if it links to an external DLL) and the Automation Interface. Using the Automation Interface you are in control of everything that goes on and you can orchestrate the exact flow of events in your application. In a custom paramter you can only answer if asked (i.e. you are a slave, EZChrom is the master). Sometimes this is good enough, but not allways.
JW
Applied Instruments
http://www.applied-instruments.com