|
I think I fixed the errors that were reported.
PLEASE.. if you get an error, let me know what the error is and more important than that, let me know what you did that caused the error.
Was it when you loaded the program or after you hit start?
If it was AFTER you hit start, then let me know what routine it was on when it did it. Restart the program and and click DEBUG to get more details. The blue bar status tells you what it was doing. Otherwise I have to figure out though thousands of line of code what crashed.
Also let me know the month and year your season is in. You can quickly find that by running my app and looking at the title bar at the top.
Just to let you know what this was, I had added a recent routine that told you what the most runs in an inning was. Like 11 runs in the 1st, 9 runs in the 2nd, etc. The error was caused if you ran it during the offseason AFTER Feb, but before the games were played. So, since my season is in July, I did not get the error. I cannot possibly try every single scenario after I add a new option.
On another side note. Keep an eye out for the runs per inning thing. I have never seen more than 11 runs in one single inning and I am wondering if it is an error on my part or if there is some kind of cap there, like when 11 runs are reached, the next batter(s) will strike out or something to prevent that from happening.
|