PDA

View Full Version : Production htr2 freeze on export

BillW
18th July 2007, 05:30.17 PM
Ken,

For the second day in a row I've had a hard freeze (power down reset required) while exporting using the production version of htr2 (2 yesterday and 1 today). After it happened yesterday, I ran 4 - 1 hour long runs of the robot to see if it is my laptop fritzing out under heat or bad RAM maybe. All ran successful.

The lockup didn't seem to occur at the same place in the export cycle.

Is it possible that a change in the data file might have shaken a sensitivity out of the woodwork? I don't really have enough evidence here to come to any conclusion but I thought Id mention it (possibly prematurely!) in case you hear of other instances.

See you next week,

Bill
DanG
18th July 2007, 05:56.31 PM
Ken,

For the second day in a row I've had a hard freeze (power down reset required) while exporting using the production version of htr2 (2 yesterday and 1 today). After it happened yesterday, I ran 4 - 1 hour long runs of the robot to see if it is my laptop fritzing out under heat or bad RAM maybe. All ran successful.

The lockup didn't seem to occur at the same place in the export cycle.

Is it possible that a change in the data file might have shaken a sensitivity out of the woodwork? I don't really have enough evidence here to come to any conclusion but I thought Id mention it (possibly prematurely!) in case you hear of other instances.

See you next week,

Bill
Bill,

Are you exporting HX3 or one of the “older” exports? If so there is an issue on export that Ken is aware of.
BillW
18th July 2007, 08:18.22 PM
Bill,

Are you exporting HX3 or one of the “older” exports? If so there is an issue on export that Ken is aware of.

I am still exporting HX3. The locks occurred in HX4, HXV and HX7 (I think?). I'll have to track down Ken's comments on HX3 - I do remember the discussion. Thanks Dan.
DanG
18th July 2007, 08:21.08 PM
I am still exporting HX3. The locks occurred in HX4, HXV and HX7 (I think?). I'll have to track down Ken's comments on HX3 - I do remember the discussion. Thanks Dan.
Bill,

Try it without HX3…I went through the same thing until I left HX3 out. Donnie experienced it with HX2.

I think Ken is trying to wean us off yesterday’s exports! :D
MikeDee
18th July 2007, 08:45.13 PM
I have exported all tracks all races since 1/1/2007 for hx4 and hx9 and no problems with the exports.

all files had results added and charts included.

I have run a few days on all exports and did not have any problems.
km
18th July 2007, 09:16.13 PM
Bill
did you read my thread "HX4 crashes older files" on this forum?
BillW
18th July 2007, 09:19.55 PM
I need to clear up confusion that I caused by not specifying which version of htr2 I was talking about (I forgot about Ken releasing htr2007). The version I was referring to is the Feb. 26, 2007, the production version I've been using all along.
BillW
18th July 2007, 09:23.17 PM
Bill
did you read my thread "HX4 crashes older files" on this forum?

Yes Ken. The files I noted the problem with were from 7/18/07 and 7/19/07.

Don't get too concerned though, as I said above, I'm still not sure it isn't a problem here. At this point I'm just making you aware. I'll continue to monitor. If I walk into the seminar sans laptop, you'll know what happened. :D

Bill
BillW
22nd July 2007, 01:56.52 AM
All has been OK since - I guess windows was just having a bad day :confused: .
tomcat
27th July 2007, 05:36.29 PM
I'm using the new db and the export of epslife bot n and r is showing 0. So
what am I doing wrong?
MikeDee
28th July 2007, 05:50.25 AM
Tom - need a few more details

Are you refering to nLIFE_EARN in hx9? Are all of the values 0 or just a few?

Are you using the template table and the Acess HX9 import specification?

The data type for this field should be set to long integer and I recall that if you are not using the import file spec these numbers can be imported incorrectly.
tomcat
28th July 2007, 08:35.17 AM
Sorry Mike,

I am referring to nEPSLIFE in HX4.
MikeDee
28th July 2007, 09:22.43 AM
similar situation Tom


nEPSlife and NEPS365 need to be set to single as they can have a decimal component. the rank should be ok set to byte or integer. These also can incorrect if you are not using the current access import file spec.
tomcat
29th July 2007, 01:57.18 PM
I changed all 4 "EPS" to single but I still get "0".
Rick
29th July 2007, 02:08.37 PM
TomCat,

You need to check out your table definitions and/or Import Specification File.

I just opened an ALL_HX4 export in Excel and under nEPSLIFE I see a range of -1 to 197326.

Looks like the field need to be Long Integer.

Of course making it Single would still work, just wasting space.

Also make sure you are using the latest version of HTR2, which is 25 Jul 07.
MikeDee
29th July 2007, 05:45.48 PM
Tom don't know why you are having a problem I just imported all races for today (Sunday) and did not have any problems there are a few 0's and -1"s.

hte -1's are FTS and I assume the 0's are hores who have not wona any money yet.

Are you getting values in the other new fields that Ken added?