It's waiting for some type of input. When an application runs unattended, it's critical that you log any errors to a file. Add some error handling with good error reporting that include PROGRAM(), LINENO(), etc.
>Hi All:
>
>I have a program that I have compiled into an EXE. It ends off with QUIT. When I execute it by double clicking the EXE, it does what it is supposed to do and exits gracefully. But when I run it from the task scheduler, it gets stuck somewhere in the program. I do not know where, since I have removed all user interface statements like SET MESSAGE. Also the config.fpw has SCREEN=OFF.
>
>Is there a rule about what statements are forbidden when running from the scheduler?
>
>Thanks,
>
>Yossi
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer