>But the address reported by Windows/Delphi is never found??! My experience with "address not found" is that the error is in a called routine that is not part of your program. That could be a call to a Windows API or it could be a Borland VCL method.
The way I normally deal with that is to step through the program in the debugger until the error is encountered. If the error is revealed by data previously not enountered, I would be useful to identify exactly which data is producing the error so that you can reliably reproduce the error. What you are going through with this is a good argument for avoiding large monolithic programs. We try to keep our programs as small and specific as possible and build them up into a large system by having programs that run other programs and use some kind of interprocess communication to talk to each other. This not only simplifies debugging, it usually vastly reduces the memory requirements of the system. I know that advice does not help with your current problem, it's just a design philosophy to think about for the future. For now, I would focus on identifying data that will reliably reproduce the problem. Once you have that, you should be able to step through the program to find the problem. Glenn Lawler www.incodesystems.com
