Yeah, right, "The "Too Many Errors" issue is resolved"", but only in my dreams. At about 12:45UTC hit the Refresh Top ResultsXML update button and poof the ValidationState=3 records were gone, no trace on the Result Status page, no way of knowing whether the friends of Mr.Cairo have done what they were supposed to do... give credit before shooting them down the rabbit's favorite hole, not to speak of not being in the current extraction set, nothing to sent to the archive db.

(As there are automaton donkeys to count with, had prudently made a backup, and retrieved the records there, so maybe tomorrow morning can see if these constitute a / the difference [Maybe these were SgtJoe's difference he posted about instead of the nightly spill, but do not know if he's doing Android crunching]

Too stupid of course to sit there and watch it, so the [partial] solution is a type of cronning:

So it's set to update every 720 minutes and then run the archiving routines [haha first run has to be synched to UTC 12:06]
but improvement on that is underway; Run at certain times:

http://www.globaliconnect.com/excel/index.php...p;catid=79&Itemid=475

BTW Did -NOT- get credit for the Too Many Errors that disappeared yesterday noon-ish [Valid but no non-error wingman to arrive in time]. This morning yet another 8.91 hours are lurking front the (A)Rabbiata hole.

Just in case, when I am visiting, now a pink button can be pushed :\

New pic of v1.4a... major blanding down on the colors and squares-saw puzzling to fit it best and logical.
http://i137.photobucket.com/albums/q210/Seker...utionApp1.40.png~original

Guess which is the most important 'square' of those? :0))

Edit: And dash-boarded, to make the square-fitting free-form rather than being locked into compromising the column width grid.

The closing off took a bit more as a popped it's incandescent light:

Rebuild the way history is contructed... rather than inserting row near top of table, verify formula are fine [Excel pulls rabbits from hats too and will happily populate them from some hidden original version], checking formula and navigating around pulling next project and next project, making it slow, just take a copy and drop the values one record down [which freezes the last record for good at that ridding of ever increasing number of index-match formula]. The beauty of this with tables being auto-extended when immediately below or right new data appears, no worries about ranges [they are with tables also auto-named per the headers]. Then, since reusing ancient code from the previous decade, found ways to half the navigation in input [costly in time factor] and again to half of that et voilá, the whole done in not under 30 seconds, not under 22, now done in 14.6 seconds. . Just the loop code:

Original code [Beetle]:

      Range("ActiveQry").Select ' Select ActiveQry, *first line of data*.
      Do While Not IsEmpty(ActiveCell) = True  ' Set Do loop to stop on first empty range cell.
        projectqry = ActiveCell.Offset(0, 0).Value
        Application.StatusBar = "Please wait, updating the Project Histories for " & projectqry
            Application.Goto Reference:=projectqry & "hist"
            ActiveCell.Offset(0, 2).Range("A1").Select
            Selection.ListObject.ListRows.Add (1)
            ActiveCell.Offset(1, 0).Range("A1:D1").Select
            Selection.Copy
            ActiveCell.Offset(-1, 0).Range("A1").Select
            ActiveSheet.Paste
            Application.CutCopyMode = False
            ActiveCell.Offset(1, 0).Range("A1:D1").Select
            Selection.Copy
            Selection.PasteSpecial Paste:=xlPasteValues, Operation:=xlNone, SkipBlanks _
                :=False, Transpose:=False
            Range("A1").Select
            Sheets("My Contrib.").Activate
            ActiveCell.Offset(1, 0).Select ' Go down 1 row from last location.
      Loop

Improved code [F1]

      Range("ActiveQry").Select ' Select ActiveQry, *first line of data*.
      Do While Not IsEmpty(ActiveCell) = True  ' Set Do loop to stop on first empty range cell.
        projectqry = ActiveCell.Offset(0, 0).Value
        Application.StatusBar = "Please wait, updating the Project Histories for " & projectqry
            Sheets(projectqry & " Qry").Activate
            Range(projectqry & "hist").Copy
            Sheets(projectqry & " Qry").Range(projectqry & "hist").Offset(1, 0).PasteSpecial Paste:=xlPasteValues
            With ActiveCell.Offset(-1, 8)
                .Select
                .ClearContents
            End With
            Sheets("My Contrib.").Activate
            ActiveCell.Offset(1, 0).Select ' Go down 1 row from last location.
      Loop

Ultimate code [F1-2017]

        For Each prj In Range("ActiveQry")
            Application.StatusBar = "Please wait, updating the Project Histories for " & prj.Value
                Sheets(prj.Value & " Qry").Activate
                Range(prj.Value & "hist").Copy
                Sheets(prj.Value & " Qry").Range(prj.Value & "hist").Offset(1, 0).PasteSpecial Paste:=xlPasteValues
                With ActiveCell.Offset(-1, 8)
                    .Select
                    .ClearContents
                End With
        Next prj

From 20 lines, to 15 lines to 10 lines, the only feedback while running in the status bar informing on which history is being extended.

Of course, exposé, the constructive criticasters can improve on this, but over at StackOverflow indications were marginal, of course, the DB is still small, but then this only adds 104 records per annum [one every 12 hours]. Arraying the Range Object would probably just take fractions off [arraying avoids accessing data repeated, transacting in memory and only when done, write the result back.

v1.5c being archived.

No, No... No, No, No, it's 10 seconds more, not 9, and the bafflement is when thinking to be really sharp and pick up the actual timestamp from the community pages to compute the 'real' spilltime... it said:

Statistics Last Updated: 7/29/15 12:06:02 (UTC) [2 hour(s) ago]

Had a task validating at 12:06:10, but it was nevertheless included in the morning results total.

Looks like the procedure order is possibly sent to a multithreaded queue and then individual processes cutting off sooner or later, but not in perfect order i.e. someone tells to take a closing timestamp, when the 4th in the relay has not crossed the line yet with the baton. [As what the techs on the science apps would refer to as a 'Race Condition'

Basically, there is for moi no programming against this, just a permanent case of throwing bloodied towels at so much consistent inconsistency [who cares anyway ].

Since, I've developed the "Recon Nook", where all tasks are listed that have a validation state = 1 and a modtime from 12:00:00 to 12:06:10 [same for the midnight block], with the totals incrementing in a second column, the total that matches the MC History page day record is the true cut-off point. I've got only few, but those that have dozens of devices will have a hard time to find which one is in and which one is out. If having dozens, you are likely only interested in ballpark anyways.

Regrettably, since there is no XML format for the history where you can specify the verification code and member name in the query, it's having to go on the website and do the old scrape to get the day record... the query now stops at the password field. So far not found a way to open the pw field, it's grayed out in the xml query connection screen on Excel, to include the tick-box 'Remember password'. I'd probably have to get into odc coding to get around that, and to be honest, not really interested iiat this time to again learn a scripting format.

Oh wait, Office uses IE as default... setting up the query a IE page showed up, with the WCG page to tick the 'Remember' box, the IE asked if I wanted the PW to be remembered or not. Did so. Exiting and launching the app, hit refresh and no PW question. Now that cookie sits there untill the cleaner comes along for it's weekly wipe.

Can't win them all, and when 'The List' item on adding the sort var for modtime to the API comes to getting a 'Done' tickmark... next decade maybe [at least, jhindo gave the impression WCG would still be there]. Right now the data arrives in received time order i.e. the spill list is not in time of change order... one more thing to fix locally I suppose.