Running the programs from a remote location, I was able to determine that Filemaker 12 does not do well with
the "import script" command. I rewrote a script removing the import command, and the problem cleared up.
Interesting, while I was doing this, I openened the force quit window under the apple icon. While Filemaker 12 was running a script, the standard message came up the Filemaker 12 was "not responding". I waited a bit, and Fielmaker 12 started (on its own) to respond, and after repeating this procedure one more time, completed the entire script.
Completing the script took a very long time.
Suggest not using the import command in scripts that will be running on a non-local computer.
"Not responding" may not mean you are "Hung" and have to force quite--just that the application is taking an extrordinarily long time to complete a particular task. FileMaker 12 is much slower than 11 in a number of reported issues and the fact that you are accessing the file remotely makes the slower responses even more painful.