🚀 go-pugleaf

> I'm running delphi developer 2, and this appears to happen way before the
first
> line of my application is executed.  From the link map, this address is
way
> outside my program, so maybe something took a wild branch into the
> stratosphere?   I reinstalled delphi, but the problem (unfortunately)
persists.

This normally happens with 3rd party or custom components that do not
initialise the properties correctly or have faulty logic in events that are
accessing properties or structures that rely on some other event being
called first. One that comes to mind is the "OnChange" event which gets
called as the component is displayed even though "logically thinking"
suggests it should not as nothing as has changed yet. It is not easy to
find the offending component. Try to remember when the problem first
occured and what non-Borland components you were working with at the time
and systematically remove and replace them until you find the offending
component. If it your own component or you have the source you will be able
to step thru in debug and find the faulty logic and correct it.

Good Hunting
Mike Heydon