-----------------
//This is for loading Arrhenius data

window -t data xyxyxy.otw;
open -w D:\Data\Test DLTS data\A28 Device\DS_000_DataMax_YG0.dat;
sec -p 0.1;
window -r %H YMax;
window -i;

window -t data xyxyxy.otw;
open -w D:\Data\Test DLTS data\A28 Device\DS_000_DataMin_YG0.dat;
sec -p 0.1;
window -r %H YMin;
window -i;

window -t data xyxyxy.otw;
open -w D:\Data\Test DLTS data\A28 Device\DS_000_DataMax_XG0.dat;
sec -p 0.1;
window -r %H XMax;
window -i;

window -t data xyxyxy.otw;
open -w D:\Data\Test DLTS data\A28 Device\DS_000_DataMin_XG0.dat;
sec -p 0.1;
window -r %H XMin;
window -i;

------------------

I've tested a simple program that opens Origin and establishes a DDE connection with it. It then sends this script fragment, with a doc -s; doc-n pair and resends indefinitely until Origin crashes. The program waits until Origin has completed execution before resending. So Origin continually loads these four datafiles, deletes them and reloads them.

In the 8 tests I did, I got failures after around 5 iterations, the quickest being three and the longest being 11. The script also crashes around this point when loaded and run manually, via a "run.file" command- though obviously it's not as easy to test an intermittent fault manually.

I've already had to put a sec -p 0.1 in there because data colums were disappearing on load. If I put a sec -p 1, it's possible that reliability increases- the maximum number of iterations rose to 24 before a crash- but it doesn't cure the problem and will make the scripts overall run too slowly.