Steema Central

When I try to print a bar chart at runtime or design time using he Print button on the Commander tool strip, I get a blue screen, and have to reboot. The same thing happens when I try to print a polar plot. I am able to print out an XY line chart without problems.

I have TeeChart v 2.0.2652.22325

Are there any known problems with TeeChart like this?

Jon

I have discovered a couple of things that seem to lead to a blue screen.

1) Place a TChart on a form. Add any random data series. Enlarge the size of the TChart object in the form, dragging the mouse just outside the form. Right click on the chart object and select Print Preview. After that dialog pops up, select Print.

This results in a blue screen for me. I don't know if it is a generic problem with the TChart library, with Microsoft Windows XP, or with the specific printer driver I am using.

2) I *think* that I have seen a blue screen if I place a plain TChart object on a form and try to print without first adding a data series.

In any case, we should not see a blue screen, but a warning message. I'll post more information as I find it.

Jon

Hi Jon,

I'm not able to reproduce this problem here. It is the first time I hear about a similar issue related to TeeChart.

I reckon there's a problem with your hardware or its device driver. Have you been able to reproduce this problem in your machine? You could also try upgrading the device driver and check if the problem persists.

Thanks in advance.

narcis wrote:Hi Jon,

I'm not able to reproduce this problem here. It is the first time I hear about a similar issue related to TeeChart.

I reckon there's a problem with your hardware or its device driver. Have you been able to reproduce this problem in your machine? You could also try upgrading the device driver and check if the problem persists.

Thanks in advance.

It may turn out that the problem I saw was a Microsoft error. I tracked down the error to this MS Knowledgebase article:

http://support.microsoft.com/kb/935843

I applied the patch and initial testing shows the problem has disappeared. I expect I'll be OK, now.

Thanks,

Jon