If you use FileMaker Server and setup a ESS you can have the ODBC tables inside your solution on FMS and put data using FIleMaker Scripts. You can use FileMaker Scheduler to run a ordinary script that moves data with Set Field in a Loop.
Task scheduler can not trigger a FileMaker script directly. I suggest two options:
1 Write a VBScript which triggers your script and add this script to the scheduler
2 Create a separate FileMaker file with a start up script running import script in the main file and schedule opening it through the Task Scheduler.
2. I tried Perform Script [Local Script] from another hosted file. It works when I run the script on my own. But when I tried it from FM Server Schedule, it gives me the error 100. [File is missing].
This one only seems to run because the local file was open at the time. It is your FileMaker Pro that recognizes that both files are open and that they can reference each other. An FMS script can not reach out to foreign machines and do things. If it could it would be a huge security issue.