Hi Greg - I will be interested to hear what some of the others have to say on this one... What I do with my own programs is to try to narrow the problem down by inserting very simple "marker" output statements at strategic points in the source code, recompiling, and studying the new output. There is surely a better way, but for me "setting traps" like that has worked. I would hate to have to do that on a program with which I was not intimately familiar though! Tough enough on my own monstrosities, let alone someone else's. Chuck Visit me at http://www.mhonline.net/~chuckh The Moon is Waxing Gibbous (61% of Full)
