Quote:
Originally Posted by Jeff P
Had that discussion yesterday with Ron Tiller at HDW.
Decided the best way to handle this is the same way we've handled all previous nonsensical track code changes track execs have told Equibase to make such as OSA, Barrett's at Fairplex, Betfair Hollywood Park, etc:
• Track code for data file names stay the same (AQU.)
• Track code for chart result file names stay the same (AQU.)
• Track code for running line and workout data stays the same (AQU.)
• Track code for all stat categories (rider, trainer, sire, damssire, etc.) stays the same (AQU.)
That way everything in the data flows.
As opposed to everything suddenly needs special handling before it can flow.
All because some track exec who doesn't bet and doesn't consider the headaches nonsensical track code changes create for customers who are actually using the data.
.
|
I don't know if it's true or not but way back many years when I asked a former racing secretary about why Oak Tree at SA got a different code when it's the same track he said it's partly because of the overall variety of the races written, and purse structure which differed intentionally from regular SA.
