Major Axis problem with Dates in OWC10

[AntiEarnie]

Try as I might I can not find anything useful on this. I am feeding a OWC chart a recordset for use in a line graph. Everything seems to plot fine on the data side and the scaling for the Y-axis works well. Problem is that OWC just does not seem to want to autoscale my x-axis properly. When using Date's I get one Major axis per timestamp. Considering there are generally at least 600 distinct timestamps in the recordset all I get is a large black mass for my x-axis lables. I can not really set a hard number for scaling since the recordsets contain arbitrary time ranges. Has anyone messed with OWC enough to have an idea on this? I've been through piles of example code from MSDN and google and I can not even find en example where someone is trying to use more then 5-10 dates.

 

[Sheco]

I don't know anything about your OWC object but I have a suggestion.

Assuming that nobody is really going to care about looking at 600 unique timestamps on the graph...

Assuming that viewers are really just looking for trends ...

You could solve this problem by changing the data that goes into your recordset. Find the min and max timestamp for the date range and then divide up the time into 5 slices. Then select your recordset according to the 5 slices.

IF you are using MSSQL server to get your data rows then take a look at the books online at the topic named Conditional Data Processing Using CASE

 

[AntiEarnie]

The only way that might work for me Sheco is if I merged the graphs together and I have not found any way to do that.

I am starting to get the impression from testing that the Office Web Components do not recognize that I am giving dates. At least that would explain why there is no auto-scaling going on for that axis. It is frustrating that the most basic of things are not documented beyond the fact that they exist... Perhaps if I could finally find the syntax for a date I could get the sucker to catch.