Quote:
Originally Posted by Jeff P
I'll display the track code on reports and pps.
The one thing track name related I do have to check at the start of each new meet is the track_name entry stored in one of my tables for purposes of parsing the Equibase Scratches and Changes XML for each track.
Equibase seems to change the track_name in the xml every time a track changes its name.
Another of those 1,000 paper cut things that need to be handled.
Imo, maintaining data integrity would be so much easier if every track were issued a genuine unique identifier (a text code, a number, it really doesn't matter) that stays the same unless a track is torn down and rebuilt from the ground up (for example River Downs and Belterra Park.)
clickable thumbnails below showing track_name Horseshoe Indianapolis
-jp
.
|
I hear you. I once programmed for a company that produced DOS software. They had a data normalization issue similar to this for their product tracking. When they changed to Windows, each type of program could have sub-types and that messed with their lack of normalization. I had warned of the issue for the year I had been there. I had to completely re-design the product tracking software... like yesterday. It was a mess. People who don't understand data don't get it.
