AnsweredAssumed Answered

defining a new field messes up imports

Question asked by gaBby on Nov 16, 2008
Latest reply on Nov 18, 2008 by TSGal

Summary

defining a new field messes up imports

Description of the issue

I just hit on another serious bug with importing, and I have tested in 8.0  8.5 and 9.0 -- it has been around a long time!! If you script an import from one FMP table to another (one or two files makes no difference), and then define a new field in the source table, FileMaker will auto-map the field as a new source field for that scripted import, so long as it can find an as-yet-unmapped field in the target table. yikes. I take it that scripted FMP-to-FMP imports are just completely not to be used? gaBby

Outcomes