fmp6:script messes up import?

[michele]

Facing a very strange phenomenon.

Import scripts that worked perfectly fine seem to 'lose' their order.

Already encountered this problem three times. At first I thought it was my mistake and started over again, but now I'm sure I didn't change anything.

Is their any explanation for this?

Haven't entered the script and confirmed a new import order. I did add fields to the tables but that shouldn't make the difference.

Anybody had the same experience? Are there things you should watch out for that might change the order?

Oh I just wish their was an easy way to view the import order and what fields it imports from, without having to run the script again. When you print the script you just see the fields that are imported to.

[Inky Phil]

Hi Michele

I am no expert but I think it is the new fields that are throwing your import order out.

As you say that should not make any difference but I remember the last time I had this problem back in 5.5 days it was the new fields that caused chaos.

I bet if you respecify your import with the new fields the problem goes away

HTH

Phil

[michele]

That's just awfull.

Read my previous question about importing 90+ fields.

That means that you can't continue to develop after you made your import scripts without having to redefine your imports over and over again.

Are there any solutions, any plugins, something..to solve this problem?

Edited January 4, 2006 by Guest

[Inky Phil]

At the time my import routine only ever applied to 1 record so I was advised in a forum to do it via script with a series of set field steps.

That way as new fields are added the import script can be modified quite easily as required. I realise that this would not be efficient for a substantial number of records.

There must be some way of avoiding the repetitiveness of respecifying the imports but I am afraid I am not experienced enough to know what it is

Phil

[Ender]

Adding fields does not affect the import order, but removing fields does.

Adjusting the import order is easy enough; simply select the Import[] script step and hit the Specify button, then adjust it as needed.

[Inky Phil]

It is coming back to me now.

The problem I had with a scripted import was when I decide to rename all my fields in order to standardise ( I started from the level of absolute beginner).

Boy did that cause me headaches trying to move the fields around in the specify box. Learnt the lesson though - avoid renaming fields where possible

Phil

[michele]

Not as easy as that when the order has completely changed. Haven't removed any fields though.

[michele]

Haven't renamed them either. Thanks for your feedback Inky Phil.

Really wonder what's going wrong.