🚀 go-pugleaf

I'm mainly writing this with the hope of saving someone some money, and
time.  I've been using Borland development products since Delphi 2 was
published.  I've relied on Borland products to build many applications,
quickly and efficiently.

I have used JBuilder 3.5, 4, 5, 6, 7, 8, 9, 10, and finally 2005.  I
purchased 2005 approximately 2 months ago.  I moved a large JBuilderX
project to 2005 with no issues.  Everything was working great until I
began using my existing datamodules in 2005.  Once I accessed a data
module I began experiencing terrible performance and stablity issues.
One data module containing 35 Query Data Sets took 13 minutes just to
open in the designer.  Another opened and when I began modifying the
class 2005 locked and crashed.

Working with Borland JBuilder support, I illustrated the problem.  They
were able to replicate it using the Welcome project and one of my data
modules.  They created a bug # 223331 acknowledging that it needed to
be corrected, and they placed a higher severity level on the bug.

They could not, and would not give me any indication of how long it
would take to fix the bug, or if it would ever be fixed.  John in
JBuilder support told me, "the data access poritions of JBuilder work,
good enough".

They've refused to refund my money, and won't provide any insight into
when this will be fixed.

Frankly based on this latest encounter with Borland support, I'm not
sure why Borland is still in business.

My warning to you is this.  If you are relying on JBuilder2005 for
development of large commerical applications, don't buy it.  Stay with
JBuilderX.  Although it has issues, it does work okay.   Borland has
been on a rampage to release new versions of JBuilder fast.  They
apparently have forgotten that developers need stable environments to
develop in.  Mission critical to Borland is apparently all about money
and less about releasing solid products.

My biggest fear in this process is that the support group within
Borland ain't talking to the development group.  John in Borland
support also told me, "development can't stop working on a new version
of JBuilder just to fix a bug".  That kind of logic belongs in a
government agency, not in a public company.