Import error

LynxPad imports individual and relay entries from semi-colon or comma delimited text files. An entry with errors is skipped and the rest import normally; when the import finishes, an Import Results dialog lists every skipped entry, so that dialog is the first place to look.

You don't need MileSplit or another entry service: you can type events and athletes into LynxPad, or import a delimited file you made yourself. For a MileSplit file, follow Getting Entries from MileSplit into LynxPad.

How to fix it

Read the Import Results dialog

  1. When the import completes, note which entries were skipped and why.
  2. The skipped records are the ones with formatting problems in the file. Fix those lines and import only them again.

Re-run the import

  1. Open the competition in LynxPad.
  2. Click File | Import, then Semi-Colon Delimited Entries… or Comma Delimited Entries….
    • This must match the delimiter in your file. A comma file imported as semi-colon, or the other way round, fails.
  3. Select the file and click Open.

Check the skipped records against the format rules

Open the delimited file in a text editor and confirm each problem record follows these rules.

  1. Every field is separated by the delimiter, and a blank field still has its delimiter. If every remaining field on a line is blank, you can end the line there.
  2. Each record ends with a carriage return / line feed (press Enter at the end of each line).
  3. The required fields are present and valid.
    • Individual (A) records need Last Name, First Name, Gender (M or F), Team Name (use Unattached if unknown), Event Number, and Event Measure (M for metric, E for English).
    • Relay (L) records need Team Name, Relay Gender (M, F or X), and Event Number; if a leg is specified, that leg's Gender is required.
  4. Marks and times are formatted correctly: times as hh:mm:ss (1:19.14, 58.43); marks as metric (12.33) or English (12-10.25").
  5. The record type letter is right: A for an individual entry, L for a relay entry. Each individual entry needs its own A record (four entries for one athlete = four A records).
  6. Fields fit the maximum lengths: Last Name and First Name 20 characters, Team Name 25, Event Number 5, Entry Mark 11. Shorten long school names or use an abbreviation.

Count the fields

  • A single missing or extra delimiter shifts every following field out of position, the most common reason a record is skipped.
  • An A record has 9 fields (A, Last Name, First Name, Gender, Team Name, Event Number, Entry Mark, Event Entry, Event Measure) and an L record has 7.
  • Compare a problem line with a record that imported successfully. The Event Entry and Event Division fields are not used by LynxPad; leave them blank.
  • Individual (A) record: A;Doe;John;M;Hurricane High School;1;21.23;M;
  • Relay (L) record: L;Hurricane High School;A;M;12;4:01.44;22;Jones;James;M;122;Stamp;Jane;F

Athletes duplicated after importing

  1. Import each entry file only once. Importing athletes again into events they are already entered in makes LynxPad treat them as new athletes.
  2. An athlete entered in several events needs one A record per event in the same file (four events = four A records), as in the format rules above.
  3. If duplicates are already in the competition, back up the competition (File | Backup…), purge the entries (File | Purge…, then check the categories to remove), and re-import one merged file with no athlete entered twice in the same event.
    • Purge permanently removes the data you check.
  4. If LynxPad shows an import error after you imported a file a second time, check the Athletes and Events windows first. The first import may already have brought everything in.

The full field tables are in Creating competition data from multiple sources in the manual.