User (Legacy) Posted March 2, 2003 Report Posted March 2, 2003 Hi, When I specify a datasource with more than 33 fields (series), chartFX randomly ignores the columns after the 33rd column, I.e. If I have 60 columns chartFX will display all of the first 33 and then any number of random columns from the last 30. This only happens when I specify CDT_VALUE and CDT_LABEL for the columns: *-- Code FOR lnC = 1 to lnF - 1 thisform.pageframe1.page1.olecontrol1.datatype[lnC] = CDT_VALUE NEXT lnC thisform.pageframe1.page1.olecontrol1.DataType[lnFieldsInCursor] = CDT_LABEL *-- /Code If I don't specify these styles (which I need to do anyway, but if I don't....) it will display all columns fine. I am using ChartFX Client Server Version 4.0.19. I have a complete sample form if someone wants to see it with their own eyes. (In VFP 7) Has anybody seen this before? Does anybody know how to fix it? Cheers, Chris.
Software FX Posted March 3, 2003 Report Posted March 3, 2003 This is a limitation. Only 32 Columns can be used in data-binding, if you data has more you will need to use alternate methods of passing data such as OpenDataEx-CloseData. Notice that there is no difference in the performance. You will just need to write a little bit more of code. -- FP Software FX, Inc.
User (Legacy) Posted March 3, 2003 Author Report Posted March 3, 2003 Thanks for that information. Is this problem documented anywhere? and Is there any particular reason why the control doesn't just give an error instead of trying to show random data? Thanks anyway for your fast answer, Chris. "SoftwareFX Support" <support@softwarefx.com> wrote in message news:0eH4vgZ4CHA.2716@webserver1.softwarefx.com... > This is a limitation. Only 32 Columns can be used in data-binding, if you > data has more you will need to use alternate methods of passing data such as > OpenDataEx-CloseData. > > Notice that there is no difference in the performance. You will just need to > write a little bit more of code. > > -- > FP > Software FX, Inc. > >
Recommended Posts
Archived
This topic is now archived and is closed to further replies.