I am converting an old FM6 appl to FM10. I have the FM6 appl export all the files into merge files. Then, the new FM10 appl imports the merge files into the .fp7 files.

When I first created the script steps, I manually selected each merge file on the Import command line and mapped the data fields to import (although I kept many of the same field names, I did change some, so I can't use a straight "matching names" import.)

The imports were fully tested and work just fine.

Here's my dilemma...

Because this needs to run on MAC & PC, I changed the Import file to use a variable $path that points to the merge files. The exported files will be on the desktop in a folder called AE_Export_v4 (which contains a FM6 runtime appl that the user will run to export the files) and subfolder Export (which contains the merge files that are exported.)

$Path is set as follows: "file:" & Get(DesktopPath) & "AE_Export_v4/Export/filename.mer" (where filename is the name of the file to import.)

This "appears" to work, however, when I go into the actual script step for the individual Imports, I no longer see the Source file or fields listed. It just shows a blank box and nothing for Source. So, even though they data is importing, I am not able to see the field mapping and verify it is correct, if I change or add a field in any of the Target tables.

With many tables and hundreds of fields involved, it is impossible to verify all the imported data after the import runs. (To be sure EVERY field is mapped correctly.)

I am including the export file folder and the new FMP10 appl (with just 1 file; I removed all relationships, the FM6 runtime appl and all other extraneous files that do not relate to the problem, to get to a manageable size to upload!!)

Thanks for any help.

AE_Export_v4.zip

FMP10_Appl.zip

I don't know of any way to verify that the fields are matching correctly other than turning on the Import dialog so that you can scan the import mapping before the import runs.

Is this a one time thing?

Edit: Btw, if you use a $var import path, you will not see the left side of the import in the script step. It's a pain, and I often include a hard-coded path to the file during testing.

Edited September 20, 200916 yr by Guest

Hm, that's what I was wondering. Thought it might be the var path. I will have to use a hard-coded path for my testing (which is what I had been doing; just switched to the var path to test that) and found the problem with not seeing the Source. What a pain!

Thanks.