v1.6a , left side a big "OKAY" as overkill to the big green tick-marked arrow. For the absentminded moments, if a tab is renamed, the program will reverse it [and some will be driven nuts by this ;p]. Though most of the background code does not care, the first 4 characters are critical to the filters working... the sheets-name is picked up by a 'UDF' (User defined Function) to lock the application short-name based filtering.

Thx, I've stuck to the long code posted in that message i.e.

=INT(H7/SecYr)&":"&RIGHT("00"&INT(MOD(H7/SecYr;1)*365);3)&":"&RIGHT("0"&INT(MOD(H7/SecHr;24));2)&":"&RIGHT("0"&INT(MOD(H7/60;60));2)&":"&RIGHT("0"&MOD(H7;60);2)

So happens OET1 went a few days ago over this critical point of 8105:140 years, thusly plugged in the old [The error check routine kicked it out :]. The hunting sheet will never ever get there, so used the elegant one with the timemask richly.

Thought to get really turbo, navigating the absolute most time consuming part in Office [slowing down VBA execution tremendously], and was doing 'in memory array copying / pasting' before writing which required the current day record notes to be erased after starting a new day. Came out, that erasing only happened time and again on prj tab 1, not on each of the project sheets, so had to get wicked (hat-tip to Useful Gyaan's 2013 post on tricks of the week) which was modded and placed at end of the For Each / Next loop:

With Application.WorksheetFunction.Index(Range(prj & "hist"), 1, Column [NotesOne]).ClearContents

Now, as bonus, does not matter where the project history is, the right record & field is being cleared on each of the processed active project sheets. LoL, being now on record 90, after 45 days of mincing the 12 hourly stats and the limit is 1,048,576 records minus 1 for the headers. The number of archived results suffers same limit, but after 10 years having done 171K+ think this will last a few years

Moving on... 99.97% complete. (Script: "If the All summary record tallies, everything else need not be marked OK too" to add.)

(This is getting towards redistributable for small crunchers... up to 5 active devices at this time, but easily extendable if the need would arise, really easy... code will be password protected though. ;o).

I am a bit curious how you eliminate the duplicates on the work fetch. I have a method of dealing with them after the download, but wonder if there is a more efficient way of dealing with them.

Cheers

Must have caused puzzle ;P

A good example of potential duplicate is this one:

OET1_ 0001063_ xSDGP-L_ rig_ 91016_ 2-- - No Reply 8/5/15 21:54:52 8/9/15 09:54:52 0.00 0.0 / 0.0 < 3) No Reply verifier not replying.
OET1_ 0001063_ xSDGP-L_ rig_ 91016_ 1-- 719 Valid 8/2/15 09:53:09 8/6/15 07:11:31 14.98 51.8 / 51.3 < 2) Verifier, Late Returner
OET1_ 0001063_ xSDGP-L_ rig_ 91016_ 0-- 719 Valid 8/1/15 09:26:50 8/2/15 09:51:56 6.01 50.7 / 51.3 < 1) in PVer

The credit was granted on the 6th when the late returner came in, but the record remained on the RS pages because there was still a task out in the wild because of _1 tardiness. The moment the 3rd copy expired, the modtime changed, so it gets listed on the current day results. Since the record was already on archive , the validator column determines to maintain 'open' state. Come archive time, 'Open' are filtered out. This will be repeated until WCG takes the record and migrates the canonical result into the master database. Since on coming cycle the modtime will fall outside the 'current' cycle, the next part of the filter, the record will fall out of active record view anyhow i.e. no distraction.

Sample formula:

=IF(OR(AND([@ValidateState]=3;[@ModTime]>PeriodStart;[@ModTime]<=PeriodEnd);AND([@Status]="Invalid";[@ModTime]>PeriodStart;[@ModTime]<=PeriodEnd;ISNA(MATCH([@Name];Archive[Result Name];0))) ;AND([@Granted]>0;[@ModTime]>PeriodStart;[@ModTime]<=PeriodEnd ;ISNA(MATCH([@Name];Archive[Result Name];0))));ActPer;"Open")

A next version will just do an index/match check based on a matrix build off server state / validate state and outcome. Just finished cycle 97, a push of 1 button (I initiates II for me), and all turned green again, so pushed III, archive, and ready we are for tomorrow morning to hit the buttons again, in that order.

As for beyond 100% complete, today added a piece of script to overlay the -highly distracting- red comment indicators with small gray triangles [hat-tip to Dana Louis of Contextures who coded this up in 2009]. Tweaked it a little to get -perfect- overlays, to the tenth of a pixel [0.1], and slide it 0.3 pixel left to not sit on top of any cell borders. This is how precise the rendering can be controlled. The color index allowed picking off 56 colors and took gray over blue. Modded to VBA further to remove any old triangles before putting new in place, [was ending up with a stag of them of varying colors, sizes, positions, while trialling for optimization].

Image of v1.6e , this time in full-screen view, so hit zoom on a wide display to feast the eye

The ranking rot has stopped, courtesy of the multi-boot which is crawling to get that 2.656GB W10 Pro downloaded via a bridged connection and the Results/Cycle curve jumped [right top graph], as the machine is doing FAAH shorties while the upgrading takes place... and not exactly in an hour, it's been running since several days before MS set the flag to start the process.