|
JCapper Message Board JCapper 101
|
| Home |
Register
Log In |
| By | Error 9 Subscript out of range while Calculating Races | |
| busseb 11/19/2008 9:52:05 AM | Got the message: "Error 9 Subscript out of range while Calculating Races" when I hit "Calculate Races". Anybody have any ideas on what I screwed up? ElPaso
| |
| ryesteve 11/19/2008 10:26:56 AM | I would blame the BRIS file, and not you.
| |
| busseb 11/19/2008 11:08:26 AM | Before the message, I had added a lot of UDM's to my list. When I tried to "Calculate Races" to see how they came up on my HTML report, I got the message early, during the export part of the calculation, I think. I know it was very early. I rebuilt my database from scratch and that went through OK but HTML report still wouldn't calculate. Deleted several UDM's from my list and now the HTML report calculates. Is there an upper limit on the number of UDM's that you are allowed? ElPaso
| |
| jeff 4/13/2013 11:24:49 AM | Bumped per new user request. Note: The upper limit was raised from 2k UDM horses flagged per calc races routine to 5k horses flagged per calc races routine some time back. However, the basic rules remain unchanged. Suggestions for avoiding a subscript out of range error during a Calc Races routine: 1. Avoid loading 20+ card files on a single folder. Instead, use the DFM Card Loader to break your race day up into 3 separate groups according to post time for R1. Load one group of 8-12 race cards all having similar post times for R1 on folder 1, a second group of 8-12 card files having similar post times for R1 on folder 2, and the remainder on folder 3. Use the multi-folder XML button interface in Scratch BOT to parse scratches from the XML for each folder separately - and use the multi-folder Calc Races buttons on the Main Module to Calc Races for each folder separately. The above strategy cuts the number of UDM "decisions" for each Calc Races routine because each Calc Races routine now involves fewer race card files. 2. Deactivate or Delete Non Essential UDMs Const USER_DEF_FILTER_UPPER_LIMIT = 5000 Const USER_DEF_PROFILE_UPPER_LIMIT = 5000 The above two lines of code in the Profile Marker define an upper limit for the number of individual UDM selections that can be made and held in memory at any one time. If there are typically 8 horses per field and 10 races per card - then a single loaded card file gives you approximately 80 horses. If you have 10 active UDMs and they collectively flag every horse in the loaded card file then 800 of the 5000 available memory slots are taken. Load a second card file, run a Calc Races, and theoretically 1600 of the 5000 slots become taken. Suggestion: Clear all loaded card files, load a single card file into the program, run a Calc Races on that card file, and count the number of individual UDM names found on the HTML Report after expanding it by clicking the +ALL characters at the top of the report. That count will give you an idea of how many loaded card files you can run a Calc Races for at any one time given your current set of active UDMs. From there, decide: 1. How many card files to load before running a Calc Races. 2. Which UDMs are absolutely neccessary for the handicapping process. Hint: deactivate UDMs you aren't really using for decision making at crunch time. Hope that helps. -jp . ~Edited by: jeff on: 4/13/2013 at: 11:24:49 AM~
|
| Reply |
|
Copyright © 2018 JCapper Software back to the JCapper Message Board www.JCapper.com |