PDA

View Full Version : HX5

Gambler
31st January 2006, 07:47.05 PM
I just downloaded HX5 template and it apperars to be wrong.
When i export into it i get several error messages.
1.nWk1gap should be nwk1_gap
2. said there is no nfnt1 field is this n1fn1

Also couldnt find the text that defined HX5.

Im i doing domething wrong.

note i also had to change rkrate to rk in HX4
ed
Rick
31st January 2006, 08:00.21 PM
The HX5.txt files and all the others has been moved to the bottom of the htr library.

I'll take a look at the other items mentioned.
Rick
31st January 2006, 08:24.16 PM
Your not doing anything wrong - its just that the exporter heading and the table headings don't match.

Mike where are you ??? :D

Looks like the template and make the HX5.txt file need some cleaning up.

What I would suggest is just changing the field names in your HX5 table to match the field names in the exporter.

I am surprised this hasn't been mentioned before.

I am also surprised that we didn't catch it before.

Thanks
Gambler
31st January 2006, 08:35.07 PM
Once again. Thanks Rick
MikeDee
1st February 2006, 06:28.29 AM
Surprise surprise!!

The only thing I can say is that when the template and hx5 txt file were issued the field names and the exporter agreed. To my knowledge the production version of the HX5 had not been changed since Oct 2003. Subsequent to this the field names where changed. I don't know why. I must have missed an update:o Perhaps Ken can shed some light on this one.

In the mean time I will revise the template and the hx5.txt file and send to Rick ASAP.

I use a custom version of HX5 daily, so I was oblivious to the change.
Cliff
1st February 2006, 03:08.40 PM
I ran into this and was thinking that the import macros somehow renamed the fields. Is that not the case?:confused:
MikeDee
1st February 2006, 04:29.16 PM
Cliff, It works the way you describe as long as you are using the import file specification. The macro in the template uses the file spec. The file spec does not care what the field name is in the export. It numbers each field from 1 to n and then you specify in the spec that field no 1 is field name "xyz" in the table.

However if you are inputting the export into the table and not using the file spec then you get the mismatch errors as the import wizard is trying to match the field name in the export, to the field name in the table.