Ken,
Q+ preparses a scan to generate 'compile-time'[actually 'interpreter-time', I suppose] errors. Runtime syntax errors occur only when a symbol has zero-vol or such that you didn't program around (EQCS comes to mind).
Some bad symbols may go undetected because they don't branch to the offending code fragment.
You should be setting daystoload [the current build will then want daysrequired also] and it's a good idea to work from an updated prescan that rejects ones like EQCS; I use the one below to screen on price and ADV[or a similar one for price*vol], and try to update the resulting scans weekly.
Would be nice if you installed the new qp2.exe -- I really hate to be the guinea pig ;) -Bob
-------------
IssueType Common; //No warrants or Pfd
float VolMin, volMA;
integer bar,VolLen;
bar:= 0; // for checking past values
VolLen := 30;
VolMin := 300; // Set here in K ************
VolMin := 1000*VolMin;
output = "300K+Vol.lst"; // Rename to match the K setting****
//ProcessMS = "d:\\junk\\escape",MSDATA;
daystoload = 2200;
DaysRequired = VolLen+1; // Will also screen out newer issues
If MovAvg(0, 5, cl) > 0 then
If MovAvg(0,VolLen,vol) > VolMin then
Println symbol,",",date(bar),",",MovAvg(bar,VolLen,vol):8:3,",",
SIC,",",DaysLoaded;
endif;
endif;
|
