label and tick mark spacing owc11

D

DuffyD

Ok, after about a week of reading "the black book" and searching google/yahoo
and this site for posts, I am finally making progress on my chart.

I have successfully converted my chart from owc9 to owc11.

Now for the problem that I am experiencing....

On my owc11 chart, it displays the data correctly, but I am experiencing
problems on the x axis. I am reading my data from the database, and I am
plotting it by date on the x axis. All of my data from the database will be
for dates that occur every 7 days- for example, there could be data on
4/28/2006, 5/5/2006, 5/12/2006, 5/19/2006, 5/26/2006, etc.
I would like an axis marker and label listed on these days on the x axis.
Unfortunately, I am getting 4/23/3006, 4/30/2006, 5/7/2006, etc for labels.
And the date is not lined up with its axis marker, but slightly off to the
right. I have no idea why.
I have played around with
.Ungroup True
on the Categories.... doesn't correct the problem.

I have played around with
Set oAxisBottom = oChart.Charts(0).Axes(oConst.chAxisPositionBottom)
With oAxisBottom
.GroupingType = chAxisGroupingNone
that doesn't help matters either.

In searching the net for other people having this problem, I found one post
that is exactly the same as what I am experiencing... but no solution listed.
http://dbforums.com/t509662.html

Any help in figuring out how to get this labelled correctly would be
appreciated.
 
D

DuffyD

More on this....
by messing around with
oConst.chAxisGroupingNone
it seems to put the dates in the wrong order on the x axis ( in the exact
same way that it was doing it in owc9).
Tried to do it on
(oConst.chAxisPositionTimescale)
and
(oConst.chAxisPositionBottom)
 
D

DuffyD

OK... this is even more goofy...
When I take the date field, and convert the "/" to a "~", it put the
tickmarks in the spots where there is data, and it labels it with the correct
date, but it sorts the dates in the incorrect order ( in the exact same way
that it was doing it in owc9).

5/5/2006, 5/19/2006, 5/26/2006, 6/2/2006, 6/9/2006, 6/23/2006, 4/28/2006,
5/12/2006, 6/16/2006

Pulling my hair out.....
 
A

Alvin Bruney [MVP]

So I suspect this issue is because of the bind to the database because I
recall seeing some other posts related to funky behavior and charts bound to
datasources.

You should either ungroup or use the "~" hash and then forcibly re-order the
data by playing with the indexes. There is an example in the black book on
how to re-order indices (somewhere, can't exactly remember where at the
moment)

--
________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
Professional VSTO.NET - Wrox/Wiley
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Blog: http://www.msmvps.com/blogs/alvin
 
D

DuffyD

Alvin,
In my last post, you told me to "add" or "bind", but not both. That was
causing my duplicate chart problem. So, I am no longer binding to the
datasource. I am walking my database query set and saving the data in 3
variables. When I have all of the data for a chartline, I do the Categories
and Values code, and use the data that is in the variables.... so at this
point, I am not binding with the set .datasource = rs.

Any other thoughts?

Alvin Bruney said:
So I suspect this issue is because of the bind to the database because I
recall seeing some other posts related to funky behavior and charts bound to
datasources.

You should either ungroup or use the "~" hash and then forcibly re-order the
data by playing with the indexes. There is an example in the black book on
how to re-order indices (somewhere, can't exactly remember where at the
moment)

--
________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
Professional VSTO.NET - Wrox/Wiley
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Blog: http://www.msmvps.com/blogs/alvin
-------------------------------------------------------


DuffyD said:
OK... this is even more goofy...
When I take the date field, and convert the "/" to a "~", it put the
tickmarks in the spots where there is data, and it labels it with the
correct
date, but it sorts the dates in the incorrect order ( in the exact same
way
that it was doing it in owc9).

5/5/2006, 5/19/2006, 5/26/2006, 6/2/2006, 6/9/2006, 6/23/2006, 4/28/2006,
5/12/2006, 6/16/2006

Pulling my hair out.....
 
D

DuffyD

In looking at this some more, it looks like the chart is listing out all
sundays on the x axis, and the dates that I am plotting are always Fridays.
Not sure if that matters (maybe some microsoft thing to always display the
first day of the week)... Who knows.

DuffyD said:
Alvin,
In my last post, you told me to "add" or "bind", but not both. That was
causing my duplicate chart problem. So, I am no longer binding to the
datasource. I am walking my database query set and saving the data in 3
variables. When I have all of the data for a chartline, I do the Categories
and Values code, and use the data that is in the variables.... so at this
point, I am not binding with the set .datasource = rs.

Any other thoughts?

Alvin Bruney said:
So I suspect this issue is because of the bind to the database because I
recall seeing some other posts related to funky behavior and charts bound to
datasources.

You should either ungroup or use the "~" hash and then forcibly re-order the
data by playing with the indexes. There is an example in the black book on
how to re-order indices (somewhere, can't exactly remember where at the
moment)

--
________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
Professional VSTO.NET - Wrox/Wiley
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Blog: http://www.msmvps.com/blogs/alvin
-------------------------------------------------------


DuffyD said:
OK... this is even more goofy...
When I take the date field, and convert the "/" to a "~", it put the
tickmarks in the spots where there is data, and it labels it with the
correct
date, but it sorts the dates in the incorrect order ( in the exact same
way
that it was doing it in owc9).

5/5/2006, 5/19/2006, 5/26/2006, 6/2/2006, 6/9/2006, 6/23/2006, 4/28/2006,
5/12/2006, 6/16/2006

Pulling my hair out.....


:

More on this....
by messing around with
oConst.chAxisGroupingNone
it seems to put the dates in the wrong order on the x axis ( in the exact
same way that it was doing it in owc9).
Tried to do it on
(oConst.chAxisPositionTimescale)
and
(oConst.chAxisPositionBottom)

:

Ok, after about a week of reading "the black book" and searching
google/yahoo
and this site for posts, I am finally making progress on my chart.

I have successfully converted my chart from owc9 to owc11.

Now for the problem that I am experiencing....

On my owc11 chart, it displays the data correctly, but I am
experiencing
problems on the x axis. I am reading my data from the database, and I
am
plotting it by date on the x axis. All of my data from the database
will be
for dates that occur every 7 days- for example, there could be data on
4/28/2006, 5/5/2006, 5/12/2006, 5/19/2006, 5/26/2006, etc.
I would like an axis marker and label listed on these days on the x
axis.
Unfortunately, I am getting 4/23/3006, 4/30/2006, 5/7/2006, etc for
labels.
And the date is not lined up with its axis marker, but slightly off to
the
right. I have no idea why.
I have played around with
.Ungroup True
on the Categories.... doesn't correct the problem.

I have played around with
Set oAxisBottom =
oChart.Charts(0).Axes(oConst.chAxisPositionBottom)
With oAxisBottom
.GroupingType = chAxisGroupingNone
that doesn't help matters either.

In searching the net for other people having this problem, I found one
post
that is exactly the same as what I am experiencing... but no solution
listed.
http://dbforums.com/t509662.html

Any help in figuring out how to get this labelled correctly would be
appreciated.
 
A

Alvin Bruney [MVP]

you need to upgroup the chart, that will disable time scaling. time scaling
assumes that sunday is the first day of the week.

--
________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
Professional VSTO.NET - Wrox/Wiley
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Blog: http://www.msmvps.com/blogs/alvin
-------------------------------------------------------


DuffyD said:
In looking at this some more, it looks like the chart is listing out all
sundays on the x axis, and the dates that I am plotting are always
Fridays.
Not sure if that matters (maybe some microsoft thing to always display the
first day of the week)... Who knows.

DuffyD said:
Alvin,
In my last post, you told me to "add" or "bind", but not both. That was
causing my duplicate chart problem. So, I am no longer binding to the
datasource. I am walking my database query set and saving the data in 3
variables. When I have all of the data for a chartline, I do the
Categories
and Values code, and use the data that is in the variables.... so at this
point, I am not binding with the set .datasource = rs.

Any other thoughts?

Alvin Bruney said:
So I suspect this issue is because of the bind to the database because
I
recall seeing some other posts related to funky behavior and charts
bound to
datasources.

You should either ungroup or use the "~" hash and then forcibly
re-order the
data by playing with the indexes. There is an example in the black book
on
how to re-order indices (somewhere, can't exactly remember where at the
moment)

--
________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
Professional VSTO.NET - Wrox/Wiley
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Blog: http://www.msmvps.com/blogs/alvin
-------------------------------------------------------


OK... this is even more goofy...
When I take the date field, and convert the "/" to a "~", it put the
tickmarks in the spots where there is data, and it labels it with the
correct
date, but it sorts the dates in the incorrect order ( in the exact
same
way
that it was doing it in owc9).

5/5/2006, 5/19/2006, 5/26/2006, 6/2/2006, 6/9/2006, 6/23/2006,
4/28/2006,
5/12/2006, 6/16/2006

Pulling my hair out.....


:

More on this....
by messing around with
oConst.chAxisGroupingNone
it seems to put the dates in the wrong order on the x axis ( in the
exact
same way that it was doing it in owc9).
Tried to do it on
(oConst.chAxisPositionTimescale)
and
(oConst.chAxisPositionBottom)

:

Ok, after about a week of reading "the black book" and searching
google/yahoo
and this site for posts, I am finally making progress on my chart.

I have successfully converted my chart from owc9 to owc11.

Now for the problem that I am experiencing....

On my owc11 chart, it displays the data correctly, but I am
experiencing
problems on the x axis. I am reading my data from the database,
and I
am
plotting it by date on the x axis. All of my data from the
database
will be
for dates that occur every 7 days- for example, there could be
data on
4/28/2006, 5/5/2006, 5/12/2006, 5/19/2006, 5/26/2006, etc.
I would like an axis marker and label listed on these days on the
x
axis.
Unfortunately, I am getting 4/23/3006, 4/30/2006, 5/7/2006, etc
for
labels.
And the date is not lined up with its axis marker, but slightly
off to
the
right. I have no idea why.
I have played around with
.Ungroup True
on the Categories.... doesn't correct the problem.

I have played around with
Set oAxisBottom =
oChart.Charts(0).Axes(oConst.chAxisPositionBottom)
With oAxisBottom
.GroupingType = chAxisGroupingNone
that doesn't help matters either.

In searching the net for other people having this problem, I found
one
post
that is exactly the same as what I am experiencing... but no
solution
listed.
http://dbforums.com/t509662.html

Any help in figuring out how to get this labelled correctly would
be
appreciated.
 
D

DuffyD

Alvin,

When I put in
'Disable time scaling on the category axis.
Set axCategory = oChart.Charts(0).Axes(oConst.chAxisPositionTimescale)
axCategory.GroupingType = oConst.chAxisGroupingNone
It creates a label on the x axis for all of the right dates (Friday instead
of Sunday), but it now reverts back to the old problem of sometime putting
the dates in the wrong order on the axis. 5/5/2006, 5/19/2006, 5/26/2006,
6/3/2006, 6/9/2006, 6/23/2006, 4/28/2006, 5/12/2006, 6/16/2006.

This was the original problem that I was trying to solve by moving from owc9
to owc11.


Alvin Bruney said:
you need to upgroup the chart, that will disable time scaling. time scaling
assumes that sunday is the first day of the week.

--
________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
Professional VSTO.NET - Wrox/Wiley
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Blog: http://www.msmvps.com/blogs/alvin
-------------------------------------------------------


DuffyD said:
In looking at this some more, it looks like the chart is listing out all
sundays on the x axis, and the dates that I am plotting are always
Fridays.
Not sure if that matters (maybe some microsoft thing to always display the
first day of the week)... Who knows.

DuffyD said:
Alvin,
In my last post, you told me to "add" or "bind", but not both. That was
causing my duplicate chart problem. So, I am no longer binding to the
datasource. I am walking my database query set and saving the data in 3
variables. When I have all of the data for a chartline, I do the
Categories
and Values code, and use the data that is in the variables.... so at this
point, I am not binding with the set .datasource = rs.

Any other thoughts?

:

So I suspect this issue is because of the bind to the database because
I
recall seeing some other posts related to funky behavior and charts
bound to
datasources.

You should either ungroup or use the "~" hash and then forcibly
re-order the
data by playing with the indexes. There is an example in the black book
on
how to re-order indices (somewhere, can't exactly remember where at the
moment)

--
________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
Professional VSTO.NET - Wrox/Wiley
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Blog: http://www.msmvps.com/blogs/alvin
-------------------------------------------------------


OK... this is even more goofy...
When I take the date field, and convert the "/" to a "~", it put the
tickmarks in the spots where there is data, and it labels it with the
correct
date, but it sorts the dates in the incorrect order ( in the exact
same
way
that it was doing it in owc9).

5/5/2006, 5/19/2006, 5/26/2006, 6/2/2006, 6/9/2006, 6/23/2006,
4/28/2006,
5/12/2006, 6/16/2006

Pulling my hair out.....


:

More on this....
by messing around with
oConst.chAxisGroupingNone
it seems to put the dates in the wrong order on the x axis ( in the
exact
same way that it was doing it in owc9).
Tried to do it on
(oConst.chAxisPositionTimescale)
and
(oConst.chAxisPositionBottom)

:

Ok, after about a week of reading "the black book" and searching
google/yahoo
and this site for posts, I am finally making progress on my chart.

I have successfully converted my chart from owc9 to owc11.

Now for the problem that I am experiencing....

On my owc11 chart, it displays the data correctly, but I am
experiencing
problems on the x axis. I am reading my data from the database,
and I
am
plotting it by date on the x axis. All of my data from the
database
will be
for dates that occur every 7 days- for example, there could be
data on
4/28/2006, 5/5/2006, 5/12/2006, 5/19/2006, 5/26/2006, etc.
I would like an axis marker and label listed on these days on the
x
axis.
Unfortunately, I am getting 4/23/3006, 4/30/2006, 5/7/2006, etc
for
labels.
And the date is not lined up with its axis marker, but slightly
off to
the
right. I have no idea why.
I have played around with
.Ungroup True
on the Categories.... doesn't correct the problem.

I have played around with
Set oAxisBottom =
oChart.Charts(0).Axes(oConst.chAxisPositionBottom)
With oAxisBottom
.GroupingType = chAxisGroupingNone
that doesn't help matters either.

In searching the net for other people having this problem, I found
one
post
that is exactly the same as what I am experiencing... but no
solution
listed.
http://dbforums.com/t509662.html

Any help in figuring out how to get this labelled correctly would
be
appreciated.
 
A

Alvin Bruney [MVP]

Seems like you are caught between a rock and a hard place huh? How about the
suggestion I provided to force the indices? Have you tried that?

--
________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
Professional VSTO.NET - Wrox/Wiley
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Blog: http://www.msmvps.com/blogs/alvin
-------------------------------------------------------


DuffyD said:
Alvin,

When I put in
'Disable time scaling on the category axis.
Set axCategory =
oChart.Charts(0).Axes(oConst.chAxisPositionTimescale)
axCategory.GroupingType = oConst.chAxisGroupingNone
It creates a label on the x axis for all of the right dates (Friday
instead
of Sunday), but it now reverts back to the old problem of sometime putting
the dates in the wrong order on the axis. 5/5/2006, 5/19/2006, 5/26/2006,
6/3/2006, 6/9/2006, 6/23/2006, 4/28/2006, 5/12/2006, 6/16/2006.

This was the original problem that I was trying to solve by moving from
owc9
to owc11.


Alvin Bruney said:
you need to upgroup the chart, that will disable time scaling. time
scaling
assumes that sunday is the first day of the week.

--
________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
Professional VSTO.NET - Wrox/Wiley
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Blog: http://www.msmvps.com/blogs/alvin
-------------------------------------------------------


DuffyD said:
In looking at this some more, it looks like the chart is listing out
all
sundays on the x axis, and the dates that I am plotting are always
Fridays.
Not sure if that matters (maybe some microsoft thing to always display
the
first day of the week)... Who knows.

:

Alvin,
In my last post, you told me to "add" or "bind", but not both. That
was
causing my duplicate chart problem. So, I am no longer binding to the
datasource. I am walking my database query set and saving the data in
3
variables. When I have all of the data for a chartline, I do the
Categories
and Values code, and use the data that is in the variables.... so at
this
point, I am not binding with the set .datasource = rs.

Any other thoughts?

:

So I suspect this issue is because of the bind to the database
because
I
recall seeing some other posts related to funky behavior and charts
bound to
datasources.

You should either ungroup or use the "~" hash and then forcibly
re-order the
data by playing with the indexes. There is an example in the black
book
on
how to re-order indices (somewhere, can't exactly remember where at
the
moment)

--
________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
Professional VSTO.NET - Wrox/Wiley
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Blog: http://www.msmvps.com/blogs/alvin
-------------------------------------------------------


OK... this is even more goofy...
When I take the date field, and convert the "/" to a "~", it put
the
tickmarks in the spots where there is data, and it labels it with
the
correct
date, but it sorts the dates in the incorrect order ( in the exact
same
way
that it was doing it in owc9).

5/5/2006, 5/19/2006, 5/26/2006, 6/2/2006, 6/9/2006, 6/23/2006,
4/28/2006,
5/12/2006, 6/16/2006

Pulling my hair out.....


:

More on this....
by messing around with
oConst.chAxisGroupingNone
it seems to put the dates in the wrong order on the x axis ( in
the
exact
same way that it was doing it in owc9).
Tried to do it on
(oConst.chAxisPositionTimescale)
and
(oConst.chAxisPositionBottom)

:

Ok, after about a week of reading "the black book" and
searching
google/yahoo
and this site for posts, I am finally making progress on my
chart.

I have successfully converted my chart from owc9 to owc11.

Now for the problem that I am experiencing....

On my owc11 chart, it displays the data correctly, but I am
experiencing
problems on the x axis. I am reading my data from the
database,
and I
am
plotting it by date on the x axis. All of my data from the
database
will be
for dates that occur every 7 days- for example, there could be
data on
4/28/2006, 5/5/2006, 5/12/2006, 5/19/2006, 5/26/2006, etc.
I would like an axis marker and label listed on these days on
the
x
axis.
Unfortunately, I am getting 4/23/3006, 4/30/2006, 5/7/2006, etc
for
labels.
And the date is not lined up with its axis marker, but slightly
off to
the
right. I have no idea why.
I have played around with
.Ungroup True
on the Categories.... doesn't correct the problem.

I have played around with
Set oAxisBottom =
oChart.Charts(0).Axes(oConst.chAxisPositionBottom)
With oAxisBottom
.GroupingType = chAxisGroupingNone
that doesn't help matters either.

In searching the net for other people having this problem, I
found
one
post
that is exactly the same as what I am experiencing... but no
solution
listed.
http://dbforums.com/t509662.html

Any help in figuring out how to get this labelled correctly
would
be
appreciated.
 
D

DuffyD

Hey Alvin,

I haven't tried forcing the indices... not exactly sure how to do that.

Any tips on that?

Alvin Bruney said:
Seems like you are caught between a rock and a hard place huh? How about the
suggestion I provided to force the indices? Have you tried that?

--
________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
Professional VSTO.NET - Wrox/Wiley
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Blog: http://www.msmvps.com/blogs/alvin
-------------------------------------------------------


DuffyD said:
Alvin,

When I put in
'Disable time scaling on the category axis.
Set axCategory =
oChart.Charts(0).Axes(oConst.chAxisPositionTimescale)
axCategory.GroupingType = oConst.chAxisGroupingNone
It creates a label on the x axis for all of the right dates (Friday
instead
of Sunday), but it now reverts back to the old problem of sometime putting
the dates in the wrong order on the axis. 5/5/2006, 5/19/2006, 5/26/2006,
6/3/2006, 6/9/2006, 6/23/2006, 4/28/2006, 5/12/2006, 6/16/2006.

This was the original problem that I was trying to solve by moving from
owc9
to owc11.


Alvin Bruney said:
you need to upgroup the chart, that will disable time scaling. time
scaling
assumes that sunday is the first day of the week.

--
________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
Professional VSTO.NET - Wrox/Wiley
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Blog: http://www.msmvps.com/blogs/alvin
-------------------------------------------------------


In looking at this some more, it looks like the chart is listing out
all
sundays on the x axis, and the dates that I am plotting are always
Fridays.
Not sure if that matters (maybe some microsoft thing to always display
the
first day of the week)... Who knows.

:

Alvin,
In my last post, you told me to "add" or "bind", but not both. That
was
causing my duplicate chart problem. So, I am no longer binding to the
datasource. I am walking my database query set and saving the data in
3
variables. When I have all of the data for a chartline, I do the
Categories
and Values code, and use the data that is in the variables.... so at
this
point, I am not binding with the set .datasource = rs.

Any other thoughts?

:

So I suspect this issue is because of the bind to the database
because
I
recall seeing some other posts related to funky behavior and charts
bound to
datasources.

You should either ungroup or use the "~" hash and then forcibly
re-order the
data by playing with the indexes. There is an example in the black
book
on
how to re-order indices (somewhere, can't exactly remember where at
the
moment)

--
________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
Professional VSTO.NET - Wrox/Wiley
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Blog: http://www.msmvps.com/blogs/alvin
-------------------------------------------------------


OK... this is even more goofy...
When I take the date field, and convert the "/" to a "~", it put
the
tickmarks in the spots where there is data, and it labels it with
the
correct
date, but it sorts the dates in the incorrect order ( in the exact
same
way
that it was doing it in owc9).

5/5/2006, 5/19/2006, 5/26/2006, 6/2/2006, 6/9/2006, 6/23/2006,
4/28/2006,
5/12/2006, 6/16/2006

Pulling my hair out.....


:

More on this....
by messing around with
oConst.chAxisGroupingNone
it seems to put the dates in the wrong order on the x axis ( in
the
exact
same way that it was doing it in owc9).
Tried to do it on
(oConst.chAxisPositionTimescale)
and
(oConst.chAxisPositionBottom)

:

Ok, after about a week of reading "the black book" and
searching
google/yahoo
and this site for posts, I am finally making progress on my
chart.

I have successfully converted my chart from owc9 to owc11.

Now for the problem that I am experiencing....

On my owc11 chart, it displays the data correctly, but I am
experiencing
problems on the x axis. I am reading my data from the
database,
and I
am
plotting it by date on the x axis. All of my data from the
database
will be
for dates that occur every 7 days- for example, there could be
data on
4/28/2006, 5/5/2006, 5/12/2006, 5/19/2006, 5/26/2006, etc.
I would like an axis marker and label listed on these days on
the
x
axis.
Unfortunately, I am getting 4/23/3006, 4/30/2006, 5/7/2006, etc
for
labels.
And the date is not lined up with its axis marker, but slightly
off to
the
right. I have no idea why.
I have played around with
.Ungroup True
on the Categories.... doesn't correct the problem.

I have played around with
Set oAxisBottom =
oChart.Charts(0).Axes(oConst.chAxisPositionBottom)
With oAxisBottom
.GroupingType = chAxisGroupingNone
that doesn't help matters either.

In searching the net for other people having this problem, I
found
one
post
that is exactly the same as what I am experiencing... but no
solution
listed.
http://dbforums.com/t509662.html

Any help in figuring out how to get this labelled correctly
would
be
appreciated.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top