Board index » delphi » Key Violations Not Returned by BDE / Paradox in Delphi 2

Key Violations Not Returned by BDE / Paradox in Delphi 2

Bug Ref: R007212

To: Darren, Developer Support
    Steve Koterski, Product Management

Bug Submitted..: Approx: 1/1/97
Solution to Bug: None Given per Borland
Actions Taken..: Darren requested that Bug Report be submitted on Delphi Bug
Report.
                 Customer issues request denied due to no such form on Web Site
and
                 that such a request was a complete waste of time.
                 No response from Borland.

Work Performed by Customer.: Post Queries on Newsgroups.
                             Visited some Borland Third Party Internet.
                             Check out Books concerning this area of question.
                             Tried updated BDE.
                             Try to ID the problem.

Solutions Found by Borland.: None
Solutions Found by Customer: Yes-Work arounds and ID the understanding of the
bug.

Results: Customer is not happy.
         Its bad for any customer to run into IDE/DE{*word*81}/COMPILER errors of
any  
         kind just on a simple error.

         I also discovered another BUG, same Delphi 2.01 IDE Freezing and EXE
on    
         entering an Invalid Time, IDE/De{*word*81} failed to ShowException on
their    
         own by default.

         Since I am trained in the Techical Support area in the company I work
for.
         It appears I have to use these procedures on Delphi itself before my  

         company's product is worked on. This is not good. Kind of makes me
think  
         should I get a job at Borland Identifying Customer Bugs and proposing  

         temporary solutions to customers and conveying bugs that need to be    

         address to the product development team or keep my job at my company
         programming and ID its products bugs. In my company, its policy to get
         back to the customers with some sort of solution to keep them moving
         forward. Its also policy to sell them updated and new features that
         ensures corporate income. We know per experience that not putting the
         customer forward will put us out of business no matter how big or
small
         the customer is.

         I have developed my own work around procedures for these two bugs.

         I hope that Delphi 3.0 has these bugs fixed. I will be checking for
them  
         as many of the people in the newsgroup will check theirs out.

         So far, I have read the Delphi Newsgroups and the Visual Basic
Newgroups.  
         The difference between the two groups is:
           o Delphi itself has lots of bugs and shortcomings to overcome in
order  
             compete with Visual. Visual addressed these problems by Version 4.
           o I am surprised that Borland has not learned from Microsofts and
other  
             third parties mistakes. You got to remember that the public is
geared  
             for basic. Delphi can't afford any blemishes. Borland must make    

             positive efforts to its community and new community members.
Otherwise
             Pascal will just die of poor attempt to maintain itself in the
market  
             and die and wither away like the other languages... The unseen and

             unheard. Remember, Basic has gotten alot of marketing behind it
from  
             Microsoft to its users. Pascal does not seem to have that... nor
can  
             it do with out it.
           o I hear that Delphi 3 will lean on the new features and not the
bugs    
             that currently plagues it.
           o The Newgroup community is so engrossed in their quest for
solutions to
             Delphi Bugs they are unhappy. Those new and entering into Delphi
may  
             resort to going to Visual because of the geometrically fewer
problems  
             it has.
           o I get a third party sending me a product notice that addresses the

             BDE. It says to not use the BDE and gain access to Microsofts Jet  

             Engine / Access Database. This is symptom of anti-delphi brewing
in a  
             pro-delphi environment.
           o The newgroups knows that Borland is Quiet for the last few months.
           o The public knows that Borland has orphened alot more products than

             Microsoft.
               Quattro Pro Dos == Great Product but got killed in the movement
to  
               Windows. Reason why... Interface change. Possibly most likely
trying
               to copy Excel and follow Word Perfect imperfect design policy.

               Word Processor (I forgot the name of it) never saw pass Version
1.

               Math Product... gone.

               Another Programming Product (Prolog) ... gone.

               DBase -- Hear nothing about it.

               Paradox --> Ophened to Corel.

             Bottom line, the pro-Borland community is getting beaten up from
these
             orphenings.

             For me I went from:
               Borland Word processor -> Borland Orphened it
               --> (20 min Word Perfect DOS hate it)
               --> (2hrs Microsoft Word DOS hate it)
               --> Amiga Word Processor (loved it)
               --> (20 Min Word Perfect Windows hate it)
               --> Microsoft Word for Windows (Love it and Staying)

               Lotus 123 --> Quattro Pro Dos (very happy-->Orphened)
                         --> Quattro Windows (very unhappy)
                         --> Microsoft Excel (Staying)

               Prolog (Never touched it --> Orphened)
               Math Product (Never touched it --> Orphened)

               Visual Basic 3.0
                 o Found Knowledgebase of thousands of bugs.
                 o Found the Database Manager was not as advance as Access 2.0
                 o Found the use interface to Visual programming yuck.
                 o Found that no rebuilding procedures unless you have Access
2.0
                 o Waited for Borland Delphi. Hoping that Borland will not make

                   Microsofts mistakes.

               --> Delphi 1.0 / 2.0 / 2.01
                 o Borland is making Microsofts mistakes and sticking by them.
                 o Visual inferface better than Visual but still needs more
work.
                 o Database desktop makes the same mistake as Microsoft.
                 o Paradox required if you wish to rebuild your database.

               DBase 3 (yuck)
               --> Paradox 3.5 (yuck)
               --> Access 1.0 (yuck)
               --> Paradox 7 (better, but using it for its rebuild or as a
better  
                             database desktop)

Awaiting your response....

 

Re:Key Violations Not Returned by BDE / Paradox in Delphi 2


Quote
harold.h...@earth.execnet.com wrote:
> Bug Ref: R007212

Harold,

As an off-line news-reader, I'm not totally happy with your ways of fighting
some personal guerilla with them in the news-group. It's just that it isn't of
general interest. You have find a work-around, so why bother anyway? Maybe
you're just smarter then they are? What did you expect from them: a weekly
report saying "sorry, we are aware of the bug, but din't solve it by yet"?

Now, publishing the work-around, that would be interesting. Maybe it could even
contribute so that it doesn't appear in the next release...

It's my impression that there are much more turning over from VB to Delphi than
the other way around, btw. And from C++...

Jasper

Re:Key Violations Not Returned by BDE / Paradox in Delphi 2


Quote
harold.h...@earth.execnet.com wrote:

> Bug Ref: R007212

> To: Darren, Developer Support
>     Steve Koterski, Product Management

> Bug Submitted..: Approx: 1/1/97
> Solution to Bug: None Given per Borland
> Actions Taken..: Darren requested that Bug Report be submitted on Delphi Bug
> Report.

<Gripe removed>

Where is the Bug Report?

Matt

Other Threads