Separation model - FM internal id or Field name

I have a solution wich is built with the separation model in mind. I have separate Interface files, br-files and data-files.

From what I understand it is nowadays no problem importing a script from one developer version of a solution to a solution out on the field if all fields mentioned in the script have been created before the actual import. Filemaker checks if the field name matches and uses it if it does.

(In FM6 this was not so - it strictly used fm internal field id which could be a issue if you had created fields in a different order etc. )

Now to my issue. I tried to exchange the interface files on a solution X with the interface files of the developer version.

Before I did that I had copied the new fields in br and data tables/files to solution X, plus imported their data.

An example here is my graphics table in the br file wich had like ten new fields or so whick now contains correct pictures.

When I had exchanged the interface files and started the now updated solution X something was wrong.

The first thing I noticed is that some of the pictures are wrong on a layout. I then looked at the graphics table on the developer and X to see some difference. I had created an additional field in X before copying from developer version, thus the internal field ids are probably displaced one "step" or so it seems.

Is this so? FM9 can pick the correct field when using script import, but not otherwise?

Edited May 5, 200817 yr by Guest