>>>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, Nadya
>
>[Dot-]Matrix printers are as graphic-able as laser or inkjet printers. Unless, of course, your office happens to have some daisy-wheel printers in use, I don't see any problem build your solution around PDFs.
>
>Anyway, what Mark suggested makes lots of sense to me, even if you don't want to use .vues in your solution. You can assemble all relevant data into a free table or group of free tables - like a snapshot of the current info status, if I can be pleonastic, probably producing redundant data just for reporting purposes - and issue the correspondent report only at print time.
>
>bye

The problem is also complexity of changes... The system is already designed and it works using RawPrint.fll. All reports, which need to be printed, use Report form to file command, then they picked up and printed by this utility. Changing whole piece of this application would not be approved by my manager anyway... :(