CompuServe Messages

I think I know where the problems are, but I wonder… can the 'window of vulnerability' be reduced to an acceptable risk level, if not eliminated altogether? There are a couple of different approaches that might do it. One that I hadn't thought of last night before you mentioned it is that you could keep your code around, perhaps modfied from its original purpose to allow a calling program to simply vector straight through to the routine. The problem then becomes one of finding a better place for it than in the middle of a lot of other in-use memory fragments. Another approach might be to SetFunction the SetFunction call itself, adding some tracking capabilities and interlocking to it.