>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?
>

Hi, Nadya, again

Something Dragan said make me wonder: why don't your batch processor reports to all printers available, one by one, and stores each report output in a table (where you could insert some control information such as date of report, printer name, stuff like this). When users decide to print a report (via the "Distribute" button) they actually choose the printer implicitly from the list of reports available in the table.

bye