Question for Borland about Rave
- From: "Peter Huisman" <p.huisman@xxxxxxxxx>
- Date: Fri, 30 Dec 2005 13:15:55 +0100
Hi,
My company has been developing with Rave and is now in the process of
upgrading all stations from D7 to D2006 and we found the following problem.
Rave cannot handle the MemoFields in win32 in D2006. This is quite
disturbing because all are projects include Rave. I asked them how and what
and I get the answer below. If this is true, why do you co-distribute this
package with Delphi! I expect some screening from Borland! This makes me
real mad, because it means that we have to stay with D7 with win32
developments (and practicly thats all we do). D2006 will probably prove to
be a costly nothing for us...
--------------------
I think you missed a very important part. ALL Borland (repeat Borland) Win32
products have a problem deep within its core on dealing with ANSI vs Wide
string. Borland has "admitted" to that problem. Danny Thorpe from Borland
(see the blog) said they have not and will not fix the area that is causing
the WideString problem. Also understand that Borland has been doing some
major work on their code with BDS 2005 and BDS 2006 releases as they make
their product work in the .NET world. Some might call it "tightening" of
their code. Even the Win32 side is affected as they have a common area
between the personalities. But they are indeed tightening many areas and not
letting as many things slip through. So anytime you try doing ANY "wide"
work on the Win32 side, you will be at risk.
The Win32 versions of Rave Reports are compiled with Delphi so we inherit
the behavior of Delphi. Rave 5 was compiled with Delphi 7 and picked up the
Delphi 7 WideString behavior. Rave 6 was compiled with BDS 2005 so it picked
up the Delphi 2005 behavior. Rave 6.5 and 7 will be compiled with BDS 2006.
We have worked hard for many years trying to be as "flexible" as possible
for dealing with multi-byte font world. However, we are trapped with what
Borland products will or will not allow. Since the "root" of the WideString
problem is with Borland we can not guarantee that any of the UTF-8, MBCS or
Unicode fonts will work with the Win32 versions of Rave Reports. If it
worked for you in Delphi 7 - it was more "luck" and not by design. For every
person (using Delphi 6 or 7) that was able to get Rave to work with MBCS, we
had dozens and dozens that were not able to do so.
I do not have any facts, but I would say Borland "found" a way to detect
TWideMemoField definition and make it use WideString which will work on the
..NET side but not on the Win32 side. You saw the result of WideStrings in
Win32. It is a double-byte and Win32 is trying to work with each byte. But
it looks like they missed the TWideStringField. I would expect that will
also be "found" and "closed" sometime in the future. Understand that Rave
simply uses the TDataSet procedures from Delphi, so if they change the
"internal" workings of TDataSet then it will affect Rave.
For your information, I have already passed your problem to the developers.
--------------------
.
- Follow-Ups:
- Re: Question for Borland about Rave
- From: Ed Dressel
- Re: Question for Borland about Rave
- Prev by Date: Re: Sponsoring Fastcode and/or FastMM4
- Next by Date: Re: $define for ProjectGroup
- Previous by thread: Sponsoring Fastcode and/or FastMM4
- Next by thread: Re: Question for Borland about Rave
- Index(es):
Relevant Pages
|
