Upgrading version 6.03 to 7 if fixes Query Designer in 6.03

rbuser

To whom it may concern

On previous upgrades there has been complications with Reports that have
been saved as binary data, etc. This caused allot of headache in terms of
upgrading clients software.

If I upgrade to version 7 from 6.03 will I have the same problems. ie; are
the reports saved in the Item Table of the DADE for version 7 exactly the
same as the reports in 6.03.

Note, I am only considering upgrading, because I still have problems with
the Query Designer not creating the correct WHERE clause for the SQL. ie;
sometimes modifying the Search criteria stuffs up the SQL WHERE. If there
is a fix for this for version 6.03 then I would prefer to have the fix.

Best regards

--
Michael Lekias
Managing Director
Professional Software Design
www.psdesign.com.au
Ph: +61 8 9444 1278
Fx: +61 8 9443 9878

digitalmetaphors

The changes which were made for RB 7 from 6.03 were architecturally related
to the report server edition and making the report engine threadsafe as well
as other enhancements to the engine and new features such as the
DBArchiveReader. The template should convert with no problems. RB 6
introduced differences in RB 5, because of Delphi 6 support. Since Delphi 7
is really not much different than Delphi 6, RB 7 didn't have to be
drastically changed like RB 6.

You could create a test machine with RB 7 demo version and see how the
reports convert. We have had no problem converting from RB 6.03 to RB 7 in
our reports for QA testing.


Cheers,

Jim Bennett
Digital Metaphors

rbuser

Hi Jim

Just didn't get an answer to my other question.

Note, I am only considering upgrading, because I still have problems with
ie;
there

Note, if I have to upgrade to 7 to have the fix, then so be it. Was this
noted as a bug in 6.03?

Cheers

--
Michael Lekias
Managing Director
Professional Software Design
www.psdesign.com.au
Ph: +61 8 9444 1278
Fx: +61 8 9443 9878

digitalmetaphors

I looked back at our conversation and I found that I was able to reproduce
your problem with the WHERE clause in RB 6.03, but not able to reproduce the
problem in RB 7 right before we released RB 7. Can you download the RB 7
demo version and give it a test drive? www.digital-metaphors.com If you can
reproduce the problem in RB 7 trial, then send me the steps to reproduce it
and I'll try it. I know you are using DBISAM, so you can send me a sample
table if that helps show the problem rather than the DBDemos paradox tables.


Cheers,

Jim Bennett
Digital Metaphors