Series Datasource DataSets combobox empty and button greyed

TeeChart VCL for Borland/CodeGear/Embarcadero RAD Studio, Delphi and C++ Builder.
Post Reply
DTXDen
Newbie
Newbie
Posts: 2
Joined: Thu Jan 20, 2005 5:00 am
Location: Texas
Contact:

Series Datasource DataSets combobox empty and button greyed

Post by DTXDen » Tue Feb 15, 2005 4:48 pm

I am having a problem with the Series Data Source tab.

No datasets appear in the combobox.

The project is a Delphi Win32 app. It originally was Delphi 6 with corresponding TeeChart VCL version.

I am recompiling with Delphi 2005 and TeeChart 7.02.

I am able to view the Form as text and edit the TAreaSeries object directly by seting DataSource = adoProcGetInvForecast - it will compile just fine and run perfectly.

adoProcGetInvForecast is a TADOStoredProcedure component which accesses a SQL Server stored procedure.

The data components are in the same module as the DBChart. I have tried re-installing TeeChart, and also tried deleting and re-adding the ADO components. The datasets still do not show up. I have created a test app and used BDE component with a TTable as a PDOX table. It still does not show any data sets.

Is there any way to repair this?

Thanks,
Den

Pep
Site Admin
Site Admin
Posts: 3299
Joined: Fri Nov 14, 2003 5:00 am
Contact:

Post by Pep » Wed Feb 16, 2005 3:37 pm

Hi Den,

yes, you're correct, I'm able to reproduce it here, it's a bug. I've added it on our defect list and a fix for it will be considered to inclusion for the next maintenance release. In meantime a workaround is to assign the DataSet via code.

KISSsoft
Newbie
Newbie
Posts: 2
Joined: Wed Feb 16, 2005 5:00 am

Post by KISSsoft » Sat Jun 04, 2005 3:12 pm

Hello,

This bug still isn't fixed in 7.04!
When will it?

I'm not able to use Teechart because of this since my project contains so much charts, setting all datasets and series by code is no option.

Dirk

Pep
Site Admin
Site Admin
Posts: 3299
Joined: Fri Nov 14, 2003 5:00 am
Contact:

Post by Pep » Thu Jun 16, 2005 11:35 am

Hi Dirk,

yes, you're correct, it still not fixed. I've put a note, and we'll do all the efforts to fix it for the next maintenance releases.

Post Reply