>Hi,
>
>A customer asked me if it is possible to run a certain procedure - actually procedure with printing many pages - unattended, automatically once a week. The only way I can think of doing it is creating a VFP application (EXE) and scheduling to run it automatically on a predetermined time. But I have never scheduled a program to run from Windows schedule. Sp. this would have to be scheduled in the Windows Server.
>Are there gotchas to watch for when doing this?

What Al said, with one major gotcha. The account under which it runs.

a) If it's a regular account, it will have to have the password changed periodically. The IT moron serving the customer will inevitably forget to enter the new password into the scheduled task, and it will silently stop running. Well, not silently, there will be entries in the event log, proudly invisible among thousands of other events. Few months later, they'll notice that it stopped working and start yelling.

b) if it's a special account with password that never expires, you will have some peace of mind until the IT guy leaves and is replaced with, or he's still there but there's a new - IT cerberus, who will throw an epileptic fit seeing an account with permanent password. He'll untick the checkbox without thinking, and also without thinking that there may be a valid reason for it and that some app depends on it... and then you're back to case a.

On my last gig I had a couple of batch things running under TScheduler, at about 20-30 servers, and one of the above happened about 3-4 times a year.