At 4/3/2003 01:11 PM, you wrote:

>I think you'll find that the problem is that AT/Scheduled tasks only get
>a limited "environment" so that the size of batch file and it's commands
>must be limited in scope.

That may very well be true, and I'll keep it in mind as the number of files
that need to be used increases. For now though, Thomas Steinmaurer
suggested specifying localhost with the connection, and it worked.

>What I have found is that you need to create a WSF (Windows Script
>File), see sample below, which runs the batch file. I then have
>AT/scheduler run the WSF file, which provides a larger environment for
>the batch file.

I'm going to keep this on hand, as it may come in useful in the near future.

Thanks again,

Bob M..