Newly defined fields auto-add to scripts?

[LDPS]

Hello all,

I'm new to FMForums. This is great!

Working in Filemaker 7.0v3. I've noticed that newly defined fields get added to previously scripted imports. How can I prevent this? thanks so much!

Sally

[Ugo DI LUCA]

Hi,

Yes, deleting fields naturally disrupt the saved import field maps, and added fields in the target table may show up as selected to receive data when custom order is used and the target table has more fields than the source.

This was a standard behaviour up to FM8.5 and I must confess that I'm not confident enough that this doesn't even occur with FileMaker 9.

One solution I have used is to hardcode the number of fields at the moment of the script creation/modification, and have the script check if the number of fields is equal to the number of items in the FieldNames ( ) function.

There have been improvements (matching names now is dynamic so that if you add fields on both sides they will be selected ), but the interface remains extremely poor I'm afraid and would certainly need a big revision IMO.

Meanwhile, does someone confirm that the issue is corrected with FM9, I haven't done a lot of import script steps I'm afraid. The fact that no answer was given within 6 hours makes me think that I'm not the only one doubting.

[mr_vodka]

Hi Ugo,

Deleting a field in the middle of the list of an import mapping will still mess up the previously stored mapping. So the answer is yes... 9 did not fix that issue. :

[Ugo DI LUCA]

Thanks John,

As for the tip mentionned, it's actually worth in the development stage only.