If the files have common account names/passwords, use open file to open the files first, then kick off the import records step. If you need to import all records from the tables, use perform script in the source files to do a show all records before importing.
Thanks, this works. It's a little slow, but works so I'm happy with it.
A key difference when importing from another file:
If the file is closed at time of import, the import records step imports all the records in the table. If it is open, you get the found set. It's ironic that FileMaker insists on the pasword dialog with each and every import records step when the file is closed. If you could access the database like all other "file open" actions--using the current file's account name and password to open the file automatically, we could do some nice imports for deploying new versions of a file that we can't do without the extra work arounds.
Hmmm, need to test this issue in FileMaker 12 to see if it still happens...