If so, the most straight-forward approach is apt to be intervening there, by modifing the scheduled task. Alternately (and perlishly), you might replace the MS schedule entry running the program, with an entry running a script.
In the latter case, you may be able to use a backtick or 'exec,' (and read carefully the third paragraph of the output of perldoc -f system for why 'system' is NOT appropriate) to execute the program with output to a .pdf printer (be that Adobe's Distiller or other .pdf printer_driver for which, on W32, you may wish to search using ppm (C:> ppm s pdf).
You could also redirect input from the program to such a script and then use one of the many .pdf modules. The same script could print the data, either from the input or from the completed .pdf, as you see fit.
More generally (as if the preceding weren't generalization enough), search and supersearch are helpful if you feed them appropriate keywords.
In reply to Re: Printing Dilemma
by ww
in thread Printing Dilemma
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |