MSFT workers

  • Thread starter Thread starter Alvin Bruney
  • Start date Start date
I've submitted this bug to microsoft Incident ID SRZ030919000818. It was
promptly closed, and I was given a mailing address to forward this bug to. I
don't know about you but requiring me to write a letter on stationary to put
in the mail virtually assumes that I am being a bother to microsoft.

Here is an edit of the bug report.

Problem Description: There appears to be a bug in the owc chart 10
component.

The Microsoft Office O.W.C. chart engine assumes that anything with a / or
a - on the x-axis is a date. How can a graphic engine make such an
assumption since it cannot conceivably know the context of the call? Values
on the x-axis are formatted like so, 09/14 the owc graphing engine appends
03 to the value making it 09/14/03. 09-14 behaves the same way. How can the
engine know what my values represent? More importantly why is the graphing
engine tampering with data. That is a
fundamental flaw.

As if this weren't bad enough, the engine scans the range of values, and if
it determines that each range is exactly 7 values apart, it immediately
assumes that these values represent weeks. But here is the horror story. The
engine then rearranges the co-ordinates so that each week now starts on a
sunday. As an example, co-ordinate (9-15,20) is re-arranged to (9-14-03,20)
and so on and so forth. I spent a lot of hours tracking down this rubbish in
my code and playing with tick labels till i got tired unable to understand
where these magical values were coming from.

An engine cannot assume that days of the week start on a sunday. At my
company, our business week begins on a tuesday and ends on a monday. Payroll
begins on a friday and ends on a thursday. Invoices now are suddenly showing
values skewed to sunday.

If i put in a range with the last value ending in 9-41, the engine doesn't
know what to do with this and either blows up or replaces ALL values on the
x-axis with rubbish.


By the way, the work around is either to replace characters in the date to
fool the engine or to turn of the automatic time scaling. There is very
little documentation on this default behavior. I learned it the hard way.


regards
--


-----------
Got TidBits?
Get it here: www.networkip.net/tidbits
Eric Gunnerson said:
It is part of our job to spend time answering customer's questions, but
different teams have different levels of committment to it. Each newsgroup
should be handle by the team that's closest to it, and we try to share
groups like dotnet.general. I spend some time on other groups that are of
interest to me

If there's a group that you think doesn't have a good MS presence, or where
you've had a problem with the answer you've gotten, please feel free to send
me an email and I'll try to get the right thing to happen. It would help if
you could send me a detailed description.

(e-mail address removed)

--
Eric Gunnerson

Visit the C# product team at http://www.csharp.net
Eric's blog is at http://blogs.gotdotnet.com/ericgu/

This posting is provided "AS IS" with no warranties, and confers no rights.
Click to expand...
 
The other way to pretty much make sure I respond to a post is to claim
that C# passes objects my reference, of course!
Click to expand...


OK, Jon. Now, see, you just gave away your secret. Now we will al
start off every message that we write with the following:

"C# passes objects my reference!"

<big grin>
 
Alvin, can you drop me an email telling me where you've asked about this?

(e-mail address removed)

--
Eric Gunnerson

Visit the C# product team at http://www.csharp.net
Eric's blog is at http://blogs.gotdotnet.com/ericgu/

This posting is provided "AS IS" with no warranties, and confers no rights.
Alvin Bruney said:
I've submitted this bug to microsoft Incident ID SRZ030919000818. It was
promptly closed, and I was given a mailing address to forward this bug to. I
don't know about you but requiring me to write a letter on stationary to put
in the mail virtually assumes that I am being a bother to microsoft.

Here is an edit of the bug report.

Problem Description: There appears to be a bug in the owc chart 10
component.

The Microsoft Office O.W.C. chart engine assumes that anything with a / or
a - on the x-axis is a date. How can a graphic engine make such an
assumption since it cannot conceivably know the context of the call? Values
on the x-axis are formatted like so, 09/14 the owc graphing engine appends
03 to the value making it 09/14/03. 09-14 behaves the same way. How can the
engine know what my values represent? More importantly why is the graphing
engine tampering with data. That is a
fundamental flaw.

As if this weren't bad enough, the engine scans the range of values, and if
it determines that each range is exactly 7 values apart, it immediately
assumes that these values represent weeks. But here is the horror story. The
engine then rearranges the co-ordinates so that each week now starts on a
sunday. As an example, co-ordinate (9-15,20) is re-arranged to (9-14-03,20)
and so on and so forth. I spent a lot of hours tracking down this rubbish in
my code and playing with tick labels till i got tired unable to understand
where these magical values were coming from.

An engine cannot assume that days of the week start on a sunday. At my
company, our business week begins on a tuesday and ends on a monday. Payroll
begins on a friday and ends on a thursday. Invoices now are suddenly showing
values skewed to sunday.

If i put in a range with the last value ending in 9-41, the engine doesn't
know what to do with this and either blows up or replaces ALL values on the
x-axis with rubbish.


By the way, the work around is either to replace characters in the date to
fool the engine or to turn of the automatic time scaling. There is very
little documentation on this default behavior. I learned it the hard way.


regards
--


-----------
Got TidBits?
Get it here: www.networkip.net/tidbits
Eric Gunnerson said:
It is part of our job to spend time answering customer's questions, but
different teams have different levels of committment to it. Each newsgroup
should be handle by the team that's closest to it, and we try to share
groups like dotnet.general. I spend some time on other groups that are of
interest to me

If there's a group that you think doesn't have a good MS presence, or where
you've had a problem with the answer you've gotten, please feel free to send
me an email and I'll try to get the right thing to happen. It would help if
you could send me a detailed description.

(e-mail address removed)

--
Eric Gunnerson

Visit the C# product team at http://www.csharp.net
Eric's blog is at http://blogs.gotdotnet.com/ericgu/

This posting is provided "AS IS" with no warranties, and confers no rights.
message news:[email protected]... a
free
Click to expand...
newsgroups.
Click to expand...
 
Back
Top