pbjohnson

I just tried that setting, and it did make things faster but it also forces me to figure out the max and set it each time I have a data set to graph so that the series data is properly scaled on the graph. This defeats the auto scaling feature which I was planning on using. any other ideas?

I did not set that property as I was hoping to use the Auto feature since the values on the Y axis may vary for this graph (and others using the same data). Once I set the Max property, I am locked into that each time I run the graph using different data, correct?

Here is the Graph in preview mode

I am evaluating ChartFX for use in our company and I am having an issue with setting the step value on the Y axis. My data values are very small numbers (0.000 to 0.020) and in order to have them appear properly on the Y axis, I must (I think) set the Step value on the Y axis to a value like .002 to display properly. When I preview the report with these settings, it looks fine. My proplem is in the Visual Studio development layout mode where the ChartFX control display seems to get confused displaying its sample data (not my actual data). The display gets messed up trying to draw the grid lines at .002 steps when the values range between 0 an 100. Even this would not be a problem except that everything I do on the chart control now takes forever each time I change something on the chart and it needs to re-display (which is a lot). Any suggestions on how to accomplish what I am trying to do without messing up the development environment and making it virtually unusable? I have added a sample of what the control looks like in VS layout mode with this step value and what it look slike in preview. Any help would be appreciated.. Thanks, Phil

I did finally resolve this issue and wanted to post a note as to what the problem was... It turned out to be a setup issue on my test machine. I was using SQL Express 2005 with Reporting services rather than a full version of SQL 2005. It seems that there are a few "behind the scenes" things that Microsoft disabled in SQL Express that cause OCX controls to not appear in the published report even though they appear just fine in preview mode... Once I upgraded to SQL 2005 Standard, everything displayed properly.... - Phil

Just a follow-up... I set up a second machine with all software (clean install of Windows 2003 server, SQL Express 2005, SQL Reporting services, VS BITS etc.) and I have the exact same problem. I noted that the config entries that you sent me were not in my config files after install of ChartFX software. I put them in and still no go. I did some research on the PublicKeyBlob method you use to allow Chart FX permission to run in the context of a report and I used the sn.exe tool to attempt to verify that the key that the config line was trying to register was actually installed properly on the machine (sn.exe -e "SoftwareFX_Strong_Name" -Tp). This utility returned an error that it could not find the name registered on my computer. Don't know if any of this will lead us in another direction, but I am still stuck with no solution for my client.... Thanks again, Phil

Andre, Thank you for the reply. I have tried the solution you recommended, but still no luck. The files were in the appropriate folders, but the 2 config files were missing the sections you highlighted. After adding them and rebooting, I was hopeful that this would work. Instead, there was no change - chart still does not appear in the report when viewed in the browser.... As this is a test machine, I am tempted to clean install everything and see if that clears everything up - but thatwould take significant time with no guarantee of success..... Anything else to try that you can think of? Thanks, Phil

Was there any resolution or recommendation for this issue? I am also evaluating ChartFX using VS 2005 and SQL Reporting services. Deployed report does not show the chart (whereas preview in the designer does). Any help would be appreciated on this as I am getting ready to purchase this product and deploy for my client... Thanks, Phil J