Page 1 of 1

Active report and TeeChart 8 Pro problem

Posted: Wed Sep 03, 2008 1:00 pm
by 15048423
Hello

We are having a problem here with Active Reports and the TeeChart 8 Pro. We are running reports for a QA scheme from a recordset, and all is well until current and archive results are rendered to the graph. This sub ParamGraph is called in the Detail_Format section of AR. The graph skips the current report graph, and renders the following participant's graph on the chart, but reports the correct parameter in the AR fields, also called in the Detail_Format section. We have not seen this before. If we render an individual report, ie, not in a recordset run, all is fine. We have tried moving the graph rendering sub, but to no avail, it has to be in the Detail_Format section to render. So, in a nutshell, Participant 1 has Participant 2 graph rendered, and so on. Any suggestions?

Thank you

David

Posted: Wed Sep 03, 2008 1:15 pm
by narcis
Hello David,

Could you please send us a simple example project we can run "as-is" to reproduce the problem here?

You can either post your files at news://www.steema.net/steema.public.attachments newsgroup or at our upload page.

Thanks in advance.

Posted: Wed Sep 03, 2008 2:08 pm
by 15048423
Hello Narcis

This is a HUGE SQL Server 2005 programme, to make a small example would take quite a while. We didn't have this problem with TeeChart 3

Posted: Wed Sep 03, 2008 3:39 pm
by 15048423
Hello Narcis

Narcis, I have "solved" the problem by inserting a page break at the end of the Active Report, all is now as it should be. Any suggestions as to why?

Regards

David

Posted: Mon Sep 08, 2008 10:27 am
by narcis
Hello David,

I'm glad to hear you solved your problem. Did you use v8.0.0.4 release for that? In that version a few changes for Active Reports were made.

Thanks in advance.

Posted: Fri Sep 26, 2008 9:48 am
by 15048423
Hello Narcis

Sorry for the delay, I have been on vacation.
Yes, I was using the new build 8.0.0.4. However, I have also taken this issue up with Data Dynamics (Active Reports), and it appears that this may be a problem with the Active Report itself. I will await further information from them in this respect.

Regards

David