>Instead of creating the report as soon as the user says to, log this request with pertinent info to a table. When they hit distribute, then prompt for the printer, and execute the report creation to the printer they select.

I thought of this and it's also quite complicated :( These jobs may be run on Friday and we want to distribute on Monday. The environment needed for report creation (tables, indexes, etc) may be already altered or deleted...

I really don't see a normal solution to this problem. PDF idea is also quite complicated and would not work for printers, which don't allow graphics (Matrix printers)...


>>Hi everybody,
>>
>>Here is the story. Main application (called JobControl) allows to run several automatic jobs in batch mode. These jobs consist of three basic steps: select data from our databases, transform them into custom output, create a report. In order to run them in batch, instead of printing reports we use REPORT FORM myReport TO FILE myFile. Later user can hit Distribute button, which allows to choose a printer, and the files are printed, using RawPrint.fll from Download section here.
>>
>>You can see our problem: reports are created with some printer set. Report to file command uses this printer info and produces file filled with codes for specific printer. Now, if user chooses the same printer, all would be fine. However, if he/she chooses another printer, garbage would be printed.
>>
>>I don't see a way to correctly solve this problem. My manager said, that we would design our reports oriented for specific printer, and user should choose this printer always. If he/she chooses another printer, it would be his/her fault. However, it's obviously not a good solution.
>>
>>Do you have ideas, how to solve this problem?
>>
>>Thanks a lot in advance.