While I haven't actually looked at the spreadsheet due to not having excel at home, as far as I can tell from reading the documentation on v3000, your macros just count the number of items added together in the time cells (hence having people input them in =1+2+3+4 format rather than just a total) and compare that to the total win/loss and spit out an error if they aren't the same thing.
Yes, that is what the Macro is doing in both the async-warning- as well as the $-tracking column.
Besides warning the user if his data-input is flawed, the calculation of various stats and their
display in the forum-codes is based on the status of these columns.
If you wanted to make this completely compatible with everything via not using macros, you could just stick like 20 cells in for each FG in some aesthetically pleasing way and just use count to do the error checking. The only real drawback to this method (assuming I guessed right about your macro use) is that the main FG page would get a bit more cluttered.
I mainly chose the input-in-a-single cell because it's so much easier and nicer to use and
because it makes the tool look as slim as possible.
Originally, several inputcells were the design. But it does clutter the Input-page where I wanted it to fit
on a single screen sparing the user to have to scroll back and forth to complete his data-input.
Also, I found searching for the cell you were at is annoying when using a table like this.
Another disavantage is that you couldn't use the tool as it is for studies like the
FG-efficiency study (
http://elementscommunity.org/forum/index.php/topic,25609.0.html) to compile the data of various users. Adding more cells manually, copy pasting
while having to highlight specific areas of the table etc. would be required.
I was actually coming to this thread to try to gauge how many people want to use this but don't have excel to figure out if I should work on putting together an equivalent project on oo.o or google docs, but it looks like you're already on top of it.
Well, there have been some complaints about Excel + Windows in this thread.
All I can say is that the Statmasta3000 was downloaded around 100 times and that
some people apparently just used it in openoffice. Don't know how many oO users
that are in the end but there will be an oO-version soon either way.
I believe I did the necessary changes in the formatting of some formulas to make
it work fine under oO. The only problem remaining is that oO uses Basic/StarBasic
for Macros and is completely incompatible with Excel-VBA.
You don't happen to know Basic?
