Hallo Gary
 MM> Weird stuff... Anyone?
 GW> Weird indeed.  I have not heard of anyone else having these
 GW> problems, so I doubt that it's Delphi itself causing the trouble. 
 GW> Perhaps there is some subtle difference in the properties or
 GW> methods of the classes you are inheriting from. 
 GW> The place to start is to create a clean, new application and a
 GW> clean, new package and insert your custom components, one at a
 GW> time, and try them out that way.
In a clean environment I do not have any more trouble than my fellow 
programmers (only the occasional access violation when closing Delphi and the 
internal error on the first compile). The trouble is, we have this battery of 
components which all need each other. You use one, you need all others, or 
your source won't compile. I know, it shouldn't be like that. Tell that to 
the senior programmer that created them :-).
I reinstalled Delphi to no avail. Writing components (and recompiling 
packages all the time) is hell. The real screwup is probably in one of my own 
components which nobody else is using. So I'll have do dig deep in a bright 
moment I guess.
Thanks for your input.
Groeten, Martin.
--- FMail/Win32 1.22
---------------