• Content count

  • Joined

  • Last visited

About tonyHarris

  • Rank
    Forum Newbie
  1. connectNullData problem

    Hi, I'm using an MSLine.swf chart with some set values structured like this "<set value='' />". I am also using the connectNullData='1' option as well. But my lines do not connect, and I get this error when viewing the chart in debug mode: ERROR: Invalid number specified in XML. FusionCharts can accept number in pure numerical form only. If your number formatting (thousand and decimal separator) is different, please specify so in XML. Also, do not add any currency symbols or other signs to the numbers. Any help would be appreciated. Thanks.
  2. I also checked the .js param list that is written to the HTML page once the chart is rendered and these are the only params that are set: <param name="allowScriptAccess" value="always" /> <param name="movie" value="../FusionCharts/FCF_Column3D.swf?ChartNoDataText=There is no data in the date range chosen, please choose another date range."/> <param name="FlashVars" value="&chartWidth=600&chartHeight=300&debugMode=0&dataXML=<graph></graph>" /> <param name="quality" value="high" /> Should the <param name="wmode" value="transparent" /> tags be in there? I have them in the FusionCharts.js file I'm using. EDIT* I noticed that the .js file works when I use the FusionCharts.RenderChart() rather than the FusionCharts.RenderChartHTML(). But I have to use the FusionCharts.RenderChartHTML() function because I'm using an UpdatePanel. EDIT* Problem fixed, I updated the .dll to the newest version and used the RenderChartHTML() function with the additional parameter for transparency. Works like a charm now.
  3. I changed the z-index of the calendar extender using this css class: < style type="text/css">.calStyle { z-index: 9999;} </style>And the calendar extender background turned transparent and was still behind the flash chart.
  4. Hi, I'm using the CalendarExtender from the AjaxControlToolKit and it appears behind the flash chart. I replaced the FusionCharts.js with the one recommended to fix this problem but it still persists. Any other suggestions or tips?