OK, I'm finally switching from repeating fields to portals. Here's one newbie problem I can't seem to solve.

The old file contained student demographics and multiple class site names. The class sites were in the dreaded repeating fields.

I created two new related files, one called Demographics and one called Class Sites. The Class Site fields show up in a portal in Demographics and create new records as they should. So far so good.

Problem: I need to import from the old file into the new Demographics file so that

-demographic data goes into fields in the Demographics file

-class site data goes into the Class Site portal fields in the Demographics file (which will also create new records in the Class Site db).

Any clues? Thanks in advance -

Mary Z

You need to do two imports. First import the demographic information that you want into the Demographics file. Then import the repeating class site info into the class site file. For the first import don't select the "break repeating fields into separate records" option. For the second import DO select this option. When you import into each file, make sure that you import whatever you are using for a key field into both files so that when you are done, the files will be properly related.

Bob, thanks so much for your help. Your solution fixed my problem.

The collective genius on this forum is amazing!!

Mary Z

Perhaps I spoke too soon.

The import of records from the old file worked. However, the key field I used (combinations of last, first names and birthdate) is not going to work when I enter more records. If the same person is entered more than once in the new db, the key field will be duplicated and things will be goofed up in the related class site db.

If I use Captain Kurt's suggestion to generate a calculated unique ID using current date, time and record, the import from the old database noted above does not work because the key field does not match.

Arrggghhhh! I'm SO tempted to go back to repeating fields! Please help!

Thanks for your patience, and pardon my ignorance.

Mary Z

Maybe you should go back to the old file, create a captkurt style unique ID there, and then redo the imports using the unique ID field as the key field.

Maybe you should go back to the old file, create a captkurt style unique ID there, and then redo the imports using the unique ID field as the key field.

Ahh, this is a GREAT idea! To fit my situation I will import old records into a "transfer" file that assigns IDs, then import into the new databases...

Thanks for talking me down from the ledge, Bob. I appreciate it.

Mary Z

Okay, but remember that you have to assign the unique ID before you split up the repeating fields, or else your files won't relate.