About the author
If you develop simple software using Delphi, you'll find that Delphi is a wonderful tool that satisfies all or most of your needs.
When you begin to develop more complex software using Delphi, you may occasionally find a glitch here or there. Most of the time, the glitch occurs because you misunderstood the documentation, or you were drunk when developing the software.
Rare is the occasion when you have stumbled onto a bug, undiscovered by anyone else. When that happens, what should you do? You can take a look at the newsgroups that Borland has set up, and see if the problems have been discussed there. If it is not, you might want to connect to Borland's newsgroups and discuss your issues there.
On the other hand, if you have either discussed the issues on the Borland newsgroups, and you want Borland to fix the bugs or issues you may have discovered, consider using QualityCentral to report the issues so that Borland may fix them.
Many of the bugs that were reported to QualityCentral were fixed. For example, in Delphi 8 Update 2, some of the bugs that were fixed were based on reports taken from QualityCentral.
An excellent article on why you should report bugs, written by Dan Miser, can be found here. Another article on the same topic can be found here, written by Nick Hodges. Nick has also written an article on “The Benefits and Truth about Quality Central”.
If you're using ActiveX or COM with either Delphi 5, 6 or 7, and have problems with the implementation, consider upgrading to Delphi 7 or Delphi 8 (which includes Delphi 7), and getting the Delphi 7 Update 1, which would be coming soon. Sources indicated that some of the issues that would be fixed in Delphi 7 Update 1 would be in the ActiveX, COM, Type Library, and ADO areas.
A method to design records so that they're allocated on a specific byte boundary, such as 16 bytes, 512 bytes, 4096 bytes, etc.