Wow, that's awesome. I looked at the api too but I'm light years away from such a hunting sheet.

Version 1.01, MC specific buttons added, right bottom and more x-chk and verification added. The device master table, just off the display right bottom, had input fields added for cores and efficiency which is taken into account to compensate for the frozen DCF at WCG and get down to the minute projection of when a target is reached, and how much could be sent back [optionals of course ;>]. Also added a recent average device production average [left of the buttons]. Shows historic average and current, 5 day average runtime and results.

http://i137.photobucket.com/albums/q210/Sekerob/MyContributionApp.png~original

Follow the link to the zoomable image [no it's not a mock up, it's now 16 half days sequential that the app tallies, including the spill [which as far as I'm concerned could be done away with... just confusing the issue]. Shows my next target is to complete 70 years, which is reached at V.Time of 16-10-15 at 15:02 (CET ;P)

Things to add:

a) A summary matrix of device and science data, again tying to the history, b) somewhere between recon table and the 12 hourly MC history. Make this a fold out object.
c) Anything else that goes

Anytime you do something new, or do something you did ages ago [like last week these days], have to check the ol library or internet. This morning, "how to get into 'edit comment' mode when the cell is underneath an object" [The noted custom action button, with the comments below to show when hovering]. Out popped this one "I wonder if even Dick Kusleika knows that one. Legend has it that the only time that Dick's fingers leave the keyboard is when he 'salutes' Excel when it crashes.). Had me rolling, but there's that long forgotten menu key on the keyboard [or Shift+F10, which also works in many other apps to replace mouse right click]: http://chandoo.org/wp/2014/01/21/right-click-from-the-keyboard-not-the-mouse/

Short story long, finally getting towards a 99 percent. Now the cosmetics and some more code cleaning to make it max robust, such as done for incrementing the 12 hour period. You can''t do that with saying LastDateValue + 0,5 Days as the comma is my local, so you have to say LastDateValue + (1 / 2), so if Dick gets the 'app' out on the toasty NW USA [Washington State], the scripts don't fall over. Similar time / date locales. Set a TimeMask, so the sweaty cruncher up in Vancouver can change my g:oo:mm:ss to d:hh:mm:ss as his locale will likely be set to US English.

New was conditional coloring of an object... the big arrow on the main sheet colors green when everything is 100% and fetches a big tickmark, turns red with an X when there's a difference to investigate [not SgtJoe's spill as that is handled], blue with IP if the period is just plain 'In Progress'.

All the gimmickry captured in a screenshot: http://i137.photobucket.com/albums/q210/Seker...utionApp1.20.png~original

It's now down to less than 30 seconds per period, if things check out, which it now has in the past 25 runs. **

Things to do:

A) Add a 'last run' time stamp below the buttons [as I once asked and got from pirogue for his WCGDAWS]... no need to keep hitting the servers as it tallied even 9 hours after the midnight stats.
B) Add "Are you Sure?" question into Archive/History routines.
C) Anything else that crops up...

** Of course, smacked right in the gob, 3 'Too Late' from previous day got removed, but credited shortly after midnight... they were still listed in the backup... 27 hours more CPU time, for the record. Need to archive these too with the nightly as the 'Too Late' credit routine seems to be running during the nightly stats, then shortly after are removed.

BTW, whilst applying a much more elegant [code efficient) transform method from seconds to WCG stats time notation, discovered that Office thru 2013 can't handle seconds notations great than 255611462399 [8105:140:23:59:59]. Add 1 second more, and the formula fails with #Value. Most WCG projects exceed this number on the cumulative. Back for those to

=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)

Instead of

=INT(H7/SecYr)&":"&RIGHT("00"&INT(MOD(H7;SecYr)/SecDay);3)&TEXT(H7/SecDay;TimeMask)

The emphasized bit, the main code improvement part.

Keep up the good work on this project. I enjoy reading of your progress. The seconds to time bug is fascinating. When I get time I think I will experiment with this item.

Cheers

The "Too Many Errors" issue is resolved [how to capture in time before they get removed from the Result Status pages]. Good night sleep and it popped right back into memory [the older you get, the really long ago memories return easier, but don't ask me about last week ;]. Remembered a discussion with uplinger about the undocumented ValidateState=3 [it still is]. I've added that to the archiving filter, so whether credit is granted or not, copy goes to history, then next round, if still there, hardly, ignore.

Did notice that the Too Late cycle does not show until the 6th copy of OET on Android finds no wingman. My _5 got the bad mark. Presume this noon will have this record as stand-out. Will probably add an additional line to the summary recon, so I don't have to spend time on checking up. [there's no 'have to', just this obsession to get it perfect so I can go back to my recliner ;p]

As for the inquiry at the MS forums, actually did get a kind mail this morning from an MVP how my long formula could be improved [full working replacement included], and yes it does read a little better:

Before:

=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)

After:

=INT(H7/SecYr)&":"&TEXT((INT(MOD(H7;SecYr)/SecDay));"000:")&TEXT(MOD(INT(H7/SecHr);24);"00:")&TEXT(MOD(INT(H7/60);60);"00:")&TEXT(MOD(H7;60);"00")

All told, 14 characters shorter, not 160 but 146. His initial solution was shorter, but he will have discovered that with the Text function you still have the rounding issue i.e. you need to use Int.

Oh, and my post did appear at their forums, with the reply. No solution/ future fix for the timemask ["your crystal ball is as good as mine"]. It's not a bug, rather 'a limitation of the formula' [ahum, there are many, but that is what coding is for... to get around]

Anyway, did apply the 'improved' formula and ran the buttons that needed pushing and was done in 22 seconds... big green connector arrow appeared with fat tickmark... The recliner is waiting, on the north face as at 33.3C now at 10:58AM, not a time to go bask in the sun. I'll push the buttons again round about 3PM. Might even script the pushing... run greens, run blues, if checking, do pink... yes, from left to right