Be aware of your bug reports in QC.
Borland is closing bug reports even if they are not fixed.
For example my Report #8445 was reported 18.06.2004.
I was so kind to also deliver the patch to fix this bug.
On the 27.06.2006 this report has been closed.
The Field "Resolution" is empty.
The Field "Resolved in Build" shows a wrong version number.
.
Relevant Pages
- Re: Delphi 8 common quality
... then your report will likely be ignored. ... are not directly monitored by Borland themselves. ... bug then perhaps it will be fixed, ... use the newsgroups, get peer support, perhaps have some Borland input ...
(borland.public.delphi.non-technical) - Re: VFP 9 and file size limits
... >since they do not report to someone. ... 1-width character field for stuff where there are allegedly only two ... empty is unambiguously "I don't know", ... which in VFP always contain at ...
(microsoft.public.fox.programmer.exchange) - RE: Can someone explain what the issue is
... How many rows are typically returned in this report - is the cube sparse, ... >> This should improve the performance of Excel MDX queries with the NON EMPTY ... >> Empty Behavior property for the calculated member. ...
(microsoft.public.sqlserver.olap) - D2005 - my first impressions
... I immediately applied the service pack. ... environment BY FAR and I have long proselytized using Borland products. ... testing been done are simply not my responsibility to report. ... Related to quality, I urge anyone to read this definition of quality ...
(borland.public.delphi.non-technical) - Old Boreland .dat File - How can I work with it?
... expereince in Access, MySQL and simillar. ... think) a DOS version of Borland. ... It has no 'custom' report so the current ... readable like an excel sheet or csv file? ...
(borland.public.delphi.non-technical) |
|
