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

DM Please continue support for D5

edited August 2002 in General
I've just been catching up with the RB 7.0 posts.

RB 7.0 will be for D6 & D7 and MAYBE D5.... And, as I understand it, there
is not going to be a bug fixing version of RB 6.03. Not that 6.03 is bad,
but there are patches for things and things that DM have said would be fixed
etc. RB 7.0 is the upgrade path.

But I am a D5 user, with no desire to go D6 or D7 (and have to upgrade all
the packages I use etc. etc.). So for me this means that Report Builder does
stop a RB6.03 :(((((

I'm not very happy about that. Am I the only RB user with D5? Would any
others like to join me in asking DM to continue support for a D5 variant?

Sarah

Comments

  • edited August 2002
    I am a D5 user with no desire to go D6 or D7 too!

    Please continue D5 support for RB!

    Wolfgang Bierl
    Strike.SoftwareSolutions

  • edited August 2002
    > I am a D5 user with no desire to go D6 or D7 too!

    we are still using D5 too.
    Major development (without RB) is still under D3
    due to component issues.


    Kind regards
    Joachim Engel.
  • edited August 2002
    Yes, we will support Delphi 5 in ReportBuilder 7. This applies to the
    Enterprise, Professional and Standard Editions. The Server Edition is
    currently relying upon Delphi 6 features requiring update pack #2 for Delphi
    6 to be installed. At this time we are only releasing the Server Edition for
    Delphi 6.


    Cheers,

    Jim Bennett
    Digital Metaphors

  • edited August 2002
    Thank you !

  • edited August 2002
    Thanks for being so responsive!
    Can understand about the server version needs. There are still a lot of
    non-server D5 apps using RB so this is fine.

  • edited August 2002
    Sarah wrote:
    does

    I'm a D5 user also, and I wish there was another minor version release
    before the jump to 7.0. There are several fixes promised that would be nice
    if they were available in version 6.

    David Miller
This discussion has been closed.