dbTalk Databases Forums  

Import Order Changing

comp.databases.filemaker comp.databases.filemaker


Discuss Import Order Changing in the comp.databases.filemaker forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
W Brent Simon
 
Posts: n/a

Default Import Order Changing - 09-08-2005 , 01:45 PM






Profile: Win XP Pro, FMP 6.0

I have a script set up to import records. The import mapping is saved to
the script. Everything works fine . . . untill I delete a field defintion
in the file that I am importing from. At this point the import mapping
becomes "corrupt" and all the fields move up one postition in the mapping.
Am I doing something wrong.

BTW : The deleted field is not one that is mapped for the import).

Reply With Quote
  #2  
Old   
FP
 
Posts: n/a

Default Re: Import Order Changing - 09-08-2005 , 06:21 PM






I've come across this often. As far as I can tell FM does the
following on import:
- in the file that your importing from, it puts the fields in creation
order
- it then gets a field count
- it does the same thing in the file that your importing into
- it then maps the field count numbers in the import script

The result of this is that if you delete the last field in the creation
order, it should be OK, but if you delete a field in the middle, your
import is messed up.

I noticed in FM7 that if I added fields to either the file I was
importing from or the file I was importing into that this also messed
up the import. Either data was imported into the new fields, or it was
taken from the new fields and imported into other fields.
I don't recall seeing this behavior in 6 but I didn't go back to find
out.

My general rule of thumb is, set the import up at the very end, if you
have to add / remove fields, redo the import.


Reply With Quote
  #3  
Old   
Peter
 
Posts: n/a

Default Re: Import Order Changing - 09-09-2005 , 03:15 AM



I've noticed the same and can honestly not understand why FM didn't map the
field order by (internal) FieldID or even Fieldname in stead of relying on
this all-too-simple scheme. I find it a very dangerous bug because you are
not always immediately aware of the unwanted results and may by that time
have done numerous imports already.

I reported this as a bug fix/feature request some time ago. The bug still
exists in 7, don't know if they finally fixed it in 8.

Regards,

Peter

On 8 Sep 2005 16:21:29 -0700, FP wrote :

Quote:
I've come across this often. As far as I can tell FM does the
following on import:
- in the file that your importing from, it puts the fields in creation
order
- it then gets a field count
- it does the same thing in the file that your importing into
- it then maps the field count numbers in the import script

The result of this is that if you delete the last field in the creation
order, it should be OK, but if you delete a field in the middle, your
import is messed up.

I noticed in FM7 that if I added fields to either the file I was
importing from or the file I was importing into that this also messed
up the import. Either data was imported into the new fields, or it was
taken from the new fields and imported into other fields.
I don't recall seeing this behavior in 6 but I didn't go back to find
out.

My general rule of thumb is, set the import up at the very end, if you
have to add / remove fields, redo the import.

Reply With Quote
  #4  
Old   
W Brent Simon
 
Posts: n/a

Default Re: Import Order Changing - 09-09-2005 , 11:20 AM



Thanks very much for both your replies. Doesnt make me any happier, but I
know that it just wasnt "just my igination, running away with me"*


*Rolling Stones
Some Girls
1978



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.