Automate Script in FileMaker

Specs:
   FileMaker Advanced Server 9
   SQL Server 2000

First, why not import from oracle direct?
Second, fm server 9 allows to schedule shell scripts AND filemaker scripts.
So do the script to import from yr SQL source, and put it in yr fm server schedule using the admin console.
Also, don't forget that fm can work on SQL sources direct without importing records, so you may work on SQL data directly (if suitable for yr app).

Q:First, why not import from oracle direct?

A:The data connection from Orcale to FileMaker is painfully slow.  So to avoid this I just run a DTS daily at night to dump the records from Oracle to MS SQL.  

"So do the script to import from yr SQL source, and put it in yr fm server schedule using the admin console."

That's what I tried to do.  I tried to schedule the script to run using the FileMaker Server Admin Console, but errors out since the most important step in my FileMaker script is "Import Records", which is not supported (i'm guessing, because the script step is not Web Compatible).

so how would i create a shell script to launch FileMaker and then launch a script within filemaker to run?

you don't have to, fm server is suppose to do it all, and import is supported in a script.
this has nothing to see with the web limitations, it is run by the server direct.
does yr sql connection need a passwd or is it saved?

Yes, my SQL connection needs a password, and this is saved in the script step of Import Records -- however, i tried to run the script via the FM Server Admin Console but it state, "ScriptMaker Script aborted"

Error      643      FILEMAKER_SERVER      Schedule "Corp_Acct_dump_from_PS" aborted; unsupported script step.

so these are the script steps in the script:

Go to Layout
Show All Records
Delete All Records [No dialog]
Import Records

And that's it...

F####### hell! you're right, I just read the doc about scheduling filemaker scripts, they are limited to web compatible actions. So > trap.
I have an old way to do this, a bit hairy, but it works (tested):
Have a fake filemaker file with only one script, set as the startup script, which calls your import script in the real database. And put this in the windows schedule of any client machine. drawback: a pc must be on, with an open session to have it work (can be locked though). You can also adapt this method by not scheduling it, and managing to get it triggered by the 1st client who connects everyday (you log it's been done and disable the script for further connections the same day).
Other way (not tested, just an idea): do it full SQL: if you set filemaker as an ODBC source (you have the adv version, so odbc is included), you can write an SQL script to read from the SQL server and write to Filemaker using a command line SQL tool for instance, and put this in the server win schedule. Or use a way you are more familiar with like php.
And about the oracle odbc access, I am surprised this is slow (never used it myself). I guess SQL server is using a direct access instead of using the odbc driver... what a waste, DB2 is the same, incredibly slow, just cannot be used on a regular base, takes ages to dump 100 lines while MSSQL or mySQL odbc drivers are damned fast.
Did you use the filemaker supplied odbc driver or anything else?

you could also have filemaker to work directly on MsSQL data wihout importing data since fm9