I'm posting this hoping it may help others who, like me, have had problems getting the full benefits from POSE's Gremlins.
Every time I launched a million Gremlins, I would end up with several odd crashes or runtime debug warnings. Alas, when I tried minimizing crash sequences, the process would often fail, and POSE would tell me that on the last run, the crash didn't occur. For years, I forgot about these sequences and instead fixed bugs I could reproduce. But I just realized (silly me) that I could do better: when I hit such an elusive crash, I start a new POSE instance with the very POSE session I used to launch the Gremlin horde in the first place, start the CW 9.3 debugger, and then launch the offending Gremlin (by its number) while under debugger control. At the expected event number, I get the crash, then I hit the Debug button and fall into my code. Due to the high number of previous events, it's sometimes hard to guess how things got to that point, but it's often easy to understand and fix the bug. Working that way, I managed to get rid of several odd crashes that had been nagging me for years. En route for the million crash-free Gremlins. I wish you the same luck. Luc Le Blanc -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
