From my experience, it tends to crash more when typing remarks, but then again, I document to death, so that's probably not relevant. I have seen it crash when typing commands of any kind, and even when NOT typing, which leads me to believe that it's not necessarily driven by user / keyboard / mouse events. From my own Windows programming experience, it is reminiscent of an array dimension error where something is reading or writing outside its defined array space, out of bounds. I agree that an overall error trap with diagnostic codes within the program is something that seems sensible if the author is serious about trying to narrow this down. For Windows to display the error instead, it seems to bypass any useful internal error trapping within the program.

I have never programmed in Delphi, so I'm not familiar with the nuances of arrays, memory allocation, or error trapping, and my thoughts may be off base in that regard.

Picster