Hi again :¬)

After testing 2058 it appears the fix was implemented this way.....

Correct handling of RangeMin>RangeMax :¬) (inverts the axes and data) but...
this means you cant  use RangeType:Automatic only RangeType::Custom

The old way to mess with the margin extent percentages does not work
I can recode to calculate my own range min and range maxes so this is a good fix for me

Many thanks

Hi David,

Many thanks for the update on this bug.  

I noticed a new service pack available 2058 today
I will go and check if the problem is fixed and i will report back later

Saddly even after following your detailed instruction on how to use the helpcenter,
It totaly fails to report anything for me, reports or bug fixes

I guess somethings gone wrong with this part of my account

I now realise this is not the place to vent frustrations over this devcenter/helpcenter thing and I will contact the people directly.

Thank you for your help.

bmcloughlin said:

FIrstly we have for over 4 years had a good tech relationship

that's why i answer your posts first whenever i see them :)

sorry that resulted in misinformation!  i should have exercised a bit more care, but i must have been overexcited about some code i was going to write.

for the link i sent you: if you visit that page, there should be a listbox on the left- click "help center" and the page should display bugs and support cases linked to your account.  unfortunately, i don't think this system can be used to look up a bug if you have never contacted Developer Support about it in the past.  I emailed DSManager about that to confirm, and will post back here if it turns out there is a way.

the system on DevCenter is no longer in use, so, sorry for the years of confusion that might have caused you.  we are migrating to a bug tracking system based on TFS, with some customer-facing pages like "my bugs," but at this time there is no equivalent page to the one you linked to.

as for 21979 - as it turns out, this is fixed in 9.2.20092.2050.  the next service release will certainly have the bug resolved.  if you need the fix earlier, i think Developer Support can provide you with an untested build if you contact them about it.

have a nice weekend!