View Single Post
  #10   Report Post  
Posted to microsoft.public.excel.programming
Ronald R. Dodge, Jr.[_2_] Ronald R. Dodge, Jr.[_2_] is offline
external usenet poster
 
Posts: 134
Default SeriesCollection Object Issue

I'm not close to that limit, as far as the 255 character limit is concerned.
However, cause of the manual work that I was doing, I had been thinking
about truncating those values down to the significant 4 digits (an
Accounting rule), then this way, I don't have mutliple lines of data to copy
from the Intermediate window either. There would be, 49 characters at most
for any one data series given 8 points potentially to plot rather than the
currently 137 characters potentially to plot. No plottable point would reach
5 digit figures [to the left of the decimal point] given current capacities
of work centers.

Thank you for those that mentioned about the chart type as that resolved the
issue. I ended up using the following snippet of code:

m_chtSetupAverageTimeLineChart.Chart.ChartType = xlColumnClustered
m_chtSetupAverageTimeLineChart.Chart.SeriesCollect ion("1st").Values = _
m_str1stShiftAverageSetupTimeConstants
m_chtSetupAverageTimeLineChart.Chart.SeriesCollect ion("3rd").Values = _
m_str3rdShiftAverageSetupTimeConstants
m_chtSetupAverageTimeLineChart.Chart.ChartType = xlLineMarkers

While I may not know any one particular area fully inside out, I'm
integrating a lot of different areas into each other including those items
outside of MS Office. Some of these things came up as a result of other
issues that I have been resolving, which I been working on making some of my
older codes more dynamic and modulated, thus I also have gotten quite deep
into Class Coding too.

What brought on me making the adjustments that had worked for years prior?
Let's just say corporate did some things that broke my reports and it's was
even to the point that I can't really rely on formulas to do certain things,
and the only way to carry the dynamicness is to use range names and refer to
them within VBA, which then that brought on some other issues along the way,
such as having to use VBA coding to manage those names.
--
Thanks,

Ronald R. Dodge, Jr.
Production Statistician
Master MOUS 2000
"Jon Peltier" wrote in message
...
It doesn't matter if the unplottable values are in a range or in an array.

Have you done the proof of concept with all values loaded into the chart
as arrays? If not, check it out before spending too much time on your
final approach. There is a limit to how long an array can be to work as
the source data for a chart series, and the limit is in the number of
characters it takes to represent the array as a string, surrounded with
curly braces and separated with commas. The limit is around 250 or so
characters.

- Jon
-------
Jon Peltier, Microsoft Excel MVP
Tutorials and Custom Solutions
Peltier Technical Services, Inc. - http://PeltierTech.com
_______


"Ronald R. Dodge, Jr." wrote in message
...
Bare in mind, I'm not assigning a range, but rather constants to the
Values property. Reason being, the plan is to eventually replicate a
copy of the worksheet from the process file to the work center file, but
then the code would then remove all external defined names from the work
center file.

If it contained just a range name, that wouldn't have been an issue, but
it's assigning constants.

--
Thanks,

Ronald R. Dodge, Jr.
Production Statistician
Master MOUS 2000
"Andy Pope" wrote in message
...
Hi,

It depends on the chart type.
I created this single line by changing the source data for a column
chart.

ActiveChart.SeriesCollection(1).Values = "=Sheet1!R2C2:R6C2"

No problem whether the range B2:B6 contains values, #N/As or is empty.

Change the chart type to Line and try using all empty or #N/A data and
it will raise a error 1004.

If your chart is not too complex you can change the type in order to
manipulate it and the return the chart type to that you want.

Cheers
Andy

Ronald R. Dodge, Jr. wrote:
If the SeriesCollection Object on the chart has all values contained
within it as "#N/A", then the object effectively becomes invisible from
the code and when attempting to set the values to it again via code, it
errors out as the code can't see the object on the Chart Object (Note,
Chart Object isn't the same object as the ChartObject Object).

However, on the spreadsheet side, one can clearly go into the
DataSource of the chart and see it there. What needs to be done to get
this issue resolved as I must still be able to print out the charts,
even if at least one of the series contains all "#N/A" values, which is
needed for interpolated charts to work properly.

For the time being, I'm having to do this manually, and I don't like
that idea.


--

Andy Pope, Microsoft MVP - Excel
http://www.andypope.info