Quote:
Originally posted by stevebsfan018
I don't want to jump on other threads, but I also don't want to create another cato thread, so sorry for asking my question on your thread.
Anyway, when I try to create the HTML, I get 'Error 13: Type Mismatch' as it tries to create the 'League Pages - Fielding Registers' page.
Has anyone had that problem before? I tried to shut it down and re-create the HTML like 5 times already, all jamming on the fielding page. Thanks!
|
I looked for this error and could only find this unanswered thread:
http://www.ootpdevelopments.com/boar...+Type+Mismatch
That means this is likely a rare/unique error so I would go back and double check you are using the correct programs with the correct version of OOTP, and following all the steps accurately.
1. If you are using OOTP5 I'd suggest using the latest version of the Cato App along with the version of CommishJoe's CSV Exporter that Jeff Cato stores on his website (
http://www.jcato.net/downloads/index.html), many people get errors when they use the Commish Joe apps that were upgraded for BOSI use.
If you already were using the correct apps listed in #1 then the next thing to try is:
2. Double check the steps described in the Cato readme (
http://www.jcato.net/downloads/history/readme5.html) - were there any steps that might have had some issues or stuff you were unsure on? If yes the source of this unique problem may be related. Also make sure you are doing one season at a time ("At this point, you can click Create HTML Files, or you can repeat these steps for the next year").
If all was okay for #2 above I would then look at the error in more detail:
3. Very important - find out exactly where the crash occurs and find out what html has been generated already. Often an application will error on a new section of commands but state the error as the last thing it completed, and in this case that would mean looking at fielding issues might be a wild goose chase - maybe the problem is what OOTP History is trying to generate next (hmmmm, that is the teams trade pages no? hmmmm....). If the error is on the next section of application code then maybe you can simply choose to not output the problem data (I forget all the OOTP History output options but there are quite a few).
Failing all that I'd ask a few general troubleshooting questions before taking a look at the data in the fielding table.
- Did you have to manually edit any of the html files from OOTP or any of the CSV files?
- Did the OOTP game generated html come from a league at exactly the pre"proceed to next year" phase?
- Did you switch versions of either OOTP (IE: OOTP4 to OOTP5), Cato History, or CommishJoe's CSV Exporter apps during the period of time you began working on the latest seasons update of Cato History?
- Have you successfully run Cato History on this league before?
- Was there any very strange events in your league, like creating a lot of players then deleting them etc.?
If none of that gets you closer to the cause of the problem maybe we could arrange it so that I could look at the DB - that has been successful with several users already, although I caution that it has also been unsuccessful with several users already
. Conversely, if you had MS Access 2000 you could also look at the data. Unless you have a very good idea of what you are looking for it is almost impossible to manually find the error (my kingdom for the VB source code
), but if you know exactly where the error occurred the problem data can usually be found, good luck!