I have two lab databases - a database of all strains currently in our lab ("lab db"), and a database of all strains that exist ("all db"). I've set up a relationship such that entering a strain name into "lab db" automatically enters information from "all db" into three different fields (call them A, B, and C). However, I need to import a file from our old db, and find that when I do, all information already entered in the A, B and C fields of the old db is lost upon import into the "lab db." [ie. if there is a match to a strain in "all db", then the info in fields A, B, and C is replaced. If there is no match, then fields A, B, and C are blank]. If I disable the relationship, then import, all is fine. But if I activate the relationship again, I lose the data in the related fields. Is there a way to prevent existing data from being over-written by data from lookups, short of creating two fields each for A, B, and C (which would clutter up my db)? Any suggestions would be greatly appreciated!

If the fields are created with Lookup values based on a relationship, when you import records FileMaker asks wheter or not you want to "Perform auto-enter options while importing". If this is checked the values from "all db" should populate your fields A, B, C. However, you can force them to be updated at any time by creating a simple script. First 'go to' the field used as the relationship key, then use the command "Relookup Field Contents". This will refresh any data in A, B, C based on the relationship to "all db"