JITpipeline EOF request

rbuser

Hi guys

I am calling the report print procedure twice without recreating the report
component. During the first call everything works fine, but on the seconde
request the report request the EOF for the JID pipeline at the end of each
page. Which it did not do during the first run.

It seems as though I need to re-initialize the report component as to reset
all internal properties. Is there a singe command I can call to do this?

Cheers
Johan

digitalmetaphors

Have you tried setting the JITPipeline.InitialIndex back to zero before each
call to Report.Print?

Cheers,

Jim Bennett
Digital Metaphors

rbuser

Thanks, but I have tried it. I do not think that the problem lies with the
JIT because the report a a whole acts strangely. For instance if I preview a
report and (Cashed and singel traversal) and forward to the last page and
then close the report and generate a the same report but with a differently
layout (Forcing a pagebreak before a new group) and then forward to the last
page stange things happens.

The first page is ok. But is does not forward to the last page as requested.
If you forward one page at a time the page numbers are not consecutive (On
page 3 end next page is 1,2,3...)

The other sinario is a master detail report with a singe master record. On
regenirating the report there are no data on pages > 1 because it checked
for the EOF of the master before reaching the EOF for the detail pipeline
(which it does not do during the first generation.)

Looking at the events sequence the JIT pl does seem to do things right but I
suspect that the report engine does not reinitialize itself correctly.

Any more Idees?

rbuser

Ok it is looking better!!!!

One silly thing was that I did not close the pipeline before regerating the
report.

The behavior of the report came right after I discovered the
ppRepot.ResetFromPageNo procedure.

Is this the best way to reset the report?

digitalmetaphors

ResetFromPageNo is an available method, but it was created specifically to
be called when drill down subreports are clicked. It will free any cached
pages. It should work, though. There is another method: Report.Reset.


Cheers,

Jim Bennett
Digital Metaphors