Bug in Script Print / Import Match Fields

Doing some disaster preparedness work, I saved a PDF copy of all my Scripts using the Script Editor's Print Button.

I was browsing through the printout, when I noticed a problem.

Several of my scripts has a Import step, and the Printout does NOT match the actual script step. For example:

The Actual Script Step:

Import Records [ Source: “file:XXX”; Target: “Events”; Method: Update matching; Add remaining; Character Set: “Mac Roman”; Field

Mapping:

Source field Serial import to Events::fkImportSerial

Source field WorkerID match with Events::WorkerID

Source field HireDate match with Events::Date

Source field kHired match with Events::EventKind

[ No dialog ]

What shows up in the Printed PDF:

Import Records [ Source: “file:XXX”; Target: “Events”; Method: Update matching; Add remaining; Character Set: “Mac Roman”; Field

Mapping:

Source field 21 import to Events::fkImportSerial

Source field 34 match with Events::WorkerID

Source field 35 match with Events::Date

Source field 60 match with Events::EventKind

Source field 79 import to Events:____ Export Fields ]

[ No dialog ]

Notice the difference: The printout has an additional ghost import field (id 79) that is being imported to a field named "____ Export Fields" (which is, in fact, a dummy global field that I'm using as a field label).

I've double-checked, and my import script step does only have 3 match fields and one import field, not 3 match fields and 2 import fields.

I see this in a few (but not all) of my scripted imports. The database seems to work fine, and no bogus data gets imported, but this is worrying.

Edited November 6, 200817 yr by Guest
updated profile to show FM 9