I'm evaluating whether to switch fr

[DianeJ]

I'm evaluating whether to switch from using Print Engine API calls in my VC++ app to using the RDC (version 8 of Crystal Reports). I've heard that Crystal is no longer going to make improvements to the Print Engine, the RDC is going to be their main integration method from now on.

I've found a couple of things that I was able to with the Print Engine API method that I haven't found a way to do with the RDC.

(1) Print an on-demand subreport. I was able to do this using the PEPrintWindow Print Engine function.

(2) Enable & disable document tool tips in the CRViewer. I was able to do this with the PEWindowOptions Print Engine structure (the showDocumentTips member).

Has anyone found a way to do these things with the RDC? Or know if they are going to be offered very shortly with the RDC in an upcoming release of Crystal Reports?

Thanks,
Diane

 

[Relloc]

In RDC you have to use WIN API calls for Print Set-up in order change print destination
If you have used the WIN API you are consequently faced with a long waiting time
If your Page counts is bigger than +/- 50 because your code needs to loop through page count as Crystal is turning out the report

The RDC also suppresses Zero’s for some strange reason from ACCESS 97 VIA CRPE you see
If isnull = true then 0 but run formula via RDC = BLANK (Tried everything)

The RDC also do not EXPORT LARGE REPORTS especially to EXEL

Bottom line after a few stressful months of using RDC the API is sure bliss