I've got a scheduled task that is supposed to execute a batch file that
is supposed to interface with a SqlAnywhere 5.0 database in order to do
create some CSV files. When I execute the batch files manually they
work fine. But when the task scheduler tries to execute the batch
files, the files don't update. According to the scheduler log, the
tasks are executing successfully, no errors. The extraction utility
that is being invoked by the batch file is reporting that the database
engine is not running. Could it be that the logged on user has an open
and available connection to the database, but the scheduled task (which
is running under a different set of credentials) has no available
connection?

I'm a SQL Server 2000 guy and know nothing about SqlAnywhere. How does
the security process for SqlAnywhere work?

Todd