"When I import, the records go to the permanent table. I added steps to add a blank record to the scratch file after I go to the layout. I go to the field for the import to start. Then I do the import. Then it works."
I've imported data into cloned files (no records) with no problem. I'm not clear as to what difference in result you're getting when you import without "creating a blank record and going to the field" vs simply importing the records.
I was stumped on this. I thought going to IMPORT LAYOUT which is in the empty scratch table would be a sufficient step to take me to the right table for importing the raw data records. But repeatedly they end up in the check register table. Luckily the imported data remains the found set to easily delete.
Also, just adding a blank record to the scratch table was not sufficient. I had to add the step of going to a field on that record.
When you manually import data, you specify the target for your import by first selecting a layout that refers to the table you want to recieve your imported data.
Let's say you want to import your data into a table named "scratch".
Select a layout that lists "scratch" in its layout setup
Do your import. In the Matching Fields Dialog, you'll see the name of the target table--the table that will receive your data listed on the right to confirm where the data will go.
When you use a script, you need to specifiy the target table when you add that step to the script by clicking Specify... in the lower right corner. You can then select the desired table from the drop down in the top right corner of the import field mapping dialog that pops up.