Thread, is this a known bug in QP2?
I have a profile containing 4 scans, all of which take different input files. They seem to run OK, but on the line in the scanner which lists which scans is currently being run, it "sticks" on scan 3. It seems to be running 4 ok, but it says it's still running scan 3.
This in and of itself wouldn't bother me, but I added a fifth scan to the profile the other day (which doesn't use an input file), and when it gets to _that_ scan, the scanner iterates through all the tickers but doesn't find a single hit. Yet, when I run this scan 5 manually or through a profile containing only it, I get on the order of 20 or so hits.
Since I do this in a batch file, I had to pull the fifth scan out of that profile, put it in its own, and run it after the "broken" profile.
Has anyone seen this before?
I'd be glad to zip up and email my scan and .prf files if anyone would care to witness this firsthand. |
