No program is bug free, and that includes Delphi and the VCL.  When a bug is 
located in the VCL, how do you make the change?
You don't want to change the original source file for several reasons.  Any 
patches that might come from Borland might expect to find the original file, 
and could croak if it has been altered.  And it's always good to have the 
original for reference.  Finally, there are indications that in Delphi 3, the 
VCL source is *not* the same source that the DCU and packages were built 
om.
If you've ever tried to change and recompile the VCL, you'll know what a 
nightmare it is.  Changes in the source often cause version mismatch errors 
when compiling.  And if you have some third party library, such as Apollo, 
that replace some of the VCL units, you'll experience even more problems.  In 
fact, Borland states that the VCL source is provided for reference only, NOT 
for rebuilding the libraries.
So when you find that show-stopping bug or memory leak in the VCL, here's 
what to do:
1. Make a subdirectory called "FIX" or something similar beneath the VCL 
source code directory.
2. Copy the original source file to the new directory and make the changes 
there.  Be sure to comment the change with a description, the date, and your 
initials.
3. Add the fixed file to your Delphi projects.  It will automatically 
override the original unit in the library.
                                ...Gary
--- GoldED 2.41
---------------