Home General
New Blog Posts: Merging Reports - Part 1 and Part 2

Problems modifying report in Windows 2000 Terminal

edited January 2008 in General
Dear support,

One of our customers is having trouble editing a report in a Windows 2000
Terminal. As I checked, it appears to be related to the fact that in a
Windows 2000 Terminal the max. number of colors is 256. When connecting to a
Windows XP or 2003 terminal using 256 colors the same problem arises.
However, when using True color the problem does not occur. Since Windows
2000 is not able to use True color in a terminal, we are unable to resolve
the problem for Windows 2000 terminal server users.

Are there any workarounds and/or is this fixable?

Thanks in advance,
Mari?lla

Comments

  • edited January 2008
    Hi Mariëlla,

    This is not a known issue. Which version of ReportBuilder are you using?
    What exactly is happening to give your customer(s) problems editing reports?

    --
    Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com

    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
  • edited January 2008
    Dear Nico,

    As I see I forgot to mention the behaviour. When modifying a report, some
    error messages "Range check error" will pop up. I am using version 10.07.

    Kind regards,
    Mari?lla

  • edited January 2008
    Hi Mariëlla,

    Which version of Windows XP are you using? I have taken a look at a number
    of our XP machines and all do not allow me to reduce the color quality to
    256. If you trace into the ReportBuilder source when the error occurs, are
    you able to see where the problem is?

    --
    Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com

    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
  • edited January 2008
    Dear Nico,

    You can connect using a remote desktop connection (mstsc.exe) and choose to
    have 256 colors (Just like a remote desktop connection to Windows 200
    _always_ is). When I'm in the office tomorrow I'll see if debugging produces
    any results.

    Thanks for so far.

    Kind regards,
    Mari?lla

  • edited January 2008
    Dear Nico,

    When the exception happens, the debugger is on the following line:

    SetPixelV(DC, Left, Top, EffectiveColor);

    File ppTBXOffice2003Theme, line 1429.

    Kind regards,
    Mari?lla

  • edited January 2008


    Try using the the defaut theme instead.

    Example:

    uses
    ppToolbarTBX;


    TppThemeManager.SetCurrentTheme('Default');



    --
    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com

    Best regards,

    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com
  • edited January 2008
    Hi Nard,

    Changing the theme (either from source or from the designer) makes the Range
    check errors disappear. Thank you! :)

    Will this be fixed in a future release of ReportBuilder or will we need this
    workaround for future versions too?

    Kind regards,
    Mari?lla

This discussion has been closed.