>>We have even thought of sending the report to an HPGL printer and capturing the output. The problem is HPGL viewers are not always of high quality and we don't have the time or desire to write our own and there is some system setup involved that the hardware group is not to hip on.
>>
>>Thoughts and suggestions please.
>
>I've posted some idea like this, but I've been off for two weeks so I don't know if anyone came up with a soulution to it. Print to fax and have the faxes sent to nowhere, but converted to graphics instead. In Windows 95 OSR2 there's a PUB: device, which is for internal use for faxing applications. It can (or at least should) be used for rendering, if anyone knew how to use it. You'll get hi-res b/w pictures, with all the pages.
>
>Still, I'd prefer something like converting .frx files into routines to generate equivalent .rtf, .doc or .htm files. Specially the .htm shouldn't be as hard to make, and surely use less space than graphics. If your users want graphics, they probably have the necessary gigabytes, but I reckon they'll choke on bandwidth sooner or later. Storing graphical info as graphics is natural, but storing character info as graphics... seems to be slaughtering an ox for a kilo of meat.


I played with the faxing to a file but the standard Microsoft fax driver is (q*&(&^)) <>. I haven't been able to make it work. I'm looking at a couple of other faxing packages. I also found a conversion from PCL to TIFF produced by Visual Software ( http://www.visual.co.uk/ ). I tried their PCL to Abobe programt and it seems okay but I'm waiting for an eval of PCL2Tiff program. One requirement we have is, is must be as difficult as possible for the user to edit the images. It is never impossible).

Fred Lauckner

You know, it works on my computer. I don't know what your problem is.

.Net aint so bad.