What happened was that the power shut off (it's on a 6-hour timer) and when we noticed, we did a save and went to turn it back on. Apparently, that save was not complete when the power came back on and it hiccupped and locked up the program. Windows wasn't locked up, but the program was stuck in an hourglass state. So, we forced a shutdown of the program and restarted it.Alizarin wrote:I tried to do what I could but since I wasn't there for the issue, I'm not sure what happened. I don't know what to say about the missing runs, so I hope nobody won their class on the last run.
The run that was lost should have been about the 8th run, as drivers had just started 8th or 9th runs when this happened. Data entry for the last 2 runs should have been after the glitch. But, it is what it is. If we only lost one run from that mess... I think we were lucky!