nCLCH

[Gambler]

I was looking at CT for 11/18/2005 the 1 & 2 race. Horse 1 in race 1 nclch is wrong. It should be 9 not 0. And in race 2 horse 1 nclch should be 13.
Ken checked the exporter for me and said it is ok. Maybe i have the field set up wrong. I have it set to numbers.
Any help would be appreciated
ed

[Rick]

TLC is showing the same thing you are saying is in the exporter.

[km]

The TLC ClCh doesn't display past one digit - I fixed that for the next version - but Ed is not concerned with the screen he is getting only one digit in the export.

I checked the nCLCH in the export (HX4) and it was definitely giving me full amounts (10, 11, 12, 13), etc.

Ed, bring up an exported HX4 file into an Excel spreadsheet and confirm for yourself that the export is working properly by scrolling over to the nCLCH column and looking at the numbers for all the horses. This will confirm that it is working properly in the export. Why your Access numbers are one digit is unknown.

Are you using HX4 in the most recent version of HTR2?

[Donnie]

One thing to look at is how wide the field may be in Access....if too short it will only show one digit if it is a two digit number. Now if he is looking at it in the table, that may be a different cause!

[Rick]

I just did an export of CT and brought it into Excel.

They are coming in as ZERO. The #1 and #2 in the 1st race are ZERO.

I checked an old table from last year and it had a range of like +22 to -16.

[Gambler]

Rick In your post rick, are you saying you seen what i seen and something is wrong. If not what are you saying.
Im looking at these values in my access table.

[Rick]

I am seeing the same thing you are seeing.

[km]

My apology Ed, you were not mistaken or going crazy! Thanks Rick for following up.

I figured it out. And now I know why the problem didn't show up anywhere but CT.

There is code that is written for Last Race SOR > 80 in order to process the CLCH.

This was a protective measure to prevent oddball races from being evaluated for the class change. In other words, if there was an error in the SOR, it would skip it, so it seeks a nominal range between 81 - 116 for the SOR in the horse's pp's.

Looking at Saturday Nov 19, CT race-1. Horses #9, #10 exit a race last time out with SOR = 80. You can view this in the PPQ and other PP screens.

It is not typical for a thoroughbred race to be awarded an SOR below 81 (very sloooow horses), but I will change the minimum to a SOR > 70 for the next update to HTR2 so these CT horses can be evaluated. If you want a copy now, I'll email you a new HTR2, but this problem will only occcur at the very cheapest tracks and the slowest of the slow races at those places. This is why no one reported this previously, it just doesn't happen at major tracks.

[Gambler]

Sure glad to hear we found the problem. I dont need any changes. I can wait till the next update.
Sure appreciate all the help. It is sure nice to have you back Rick.
Thanks
ed

[Rick]

Ed,
It is nice to be back.

And thanks to you for finding this.

All I try to do is try to duplicate the problem and verify it. Some times I am able to figure out what the problem is and times like this I am not.

But km is normally pretty good at figuring out what is the problem when something is not right.

[Rick]

"Nov 19 version of HTR2.exe is available for download with the patch for the nCLCH problem in the export and TLC screen"
km

http://www.homebased2.com/km/dnl/htr2.exe

[Gambler]

WOW!!!!!!!
Thanks
ed