Martin Maat mentioned this to Gary Weinfurther:
 MM> In a clean environment I do not have any more trouble than my fellow
 MM> programmers (only the occasional access violation when closing Delphi 
nd
 MM> the internal error on the first compile).
Make sure all the compiler checking is on (range checking, stack checking, 
etc.).  Get Memory Sleuth from TurboPower Software or NuMega BoundsChecker to 
help identify leaks and overwrites.
 MM> The trouble is, we have this
 MM> battery of components which all need each other. You use one, you need 
all
 MM> others, or your source won't compile. I know, it shouldn't be like that.
Yes, the idea behind components is to make them self-sufficient.  That helps 
to identify and prevent problems such as those you are now facing.  The way 
to interface separate components is through the use of component events.
                                ...Gary
--- GoldED 2.41
---------------