CR of VS 2005 always prints as image; need EMF etc
After Crystal Reports XI, we had the problem that our printing software got more and more bugs and we where informed that old versions where no longer supported, so we should rewrite our software with one of the new interfaces. We choosed the .NET one.
However, our new printing frame now seems to always print using an image, i.e. the output file to the printer is just a bitmap. Even the output to Postscript printers is just that, an embedded image. While this is often no issue, some of our clients use printing to virtual printers, such as fax software, or archivation software etc. They therefore parse the output file for various informations not available if its just an image.
Printing from CR XI itself, and from our old software still based on the C interface (crpe32.dll) works fine. So clearly CR is able to produce more intelligent output formats. What can be done to enforce using them ?