![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
#3
| |||
| |||
|
|
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. |
#4
| |||
| |||
|
![]() |
| Thread Tools | |
| Display Modes | |
| |