I just tried it out. I created a form with a number of other controls on it, and made the MousePointer for the form an hourglass. As long as the mouse cursor is over the form itself, it remains an hourglass. I change it back to default in the form Destroy().

I can only assume it's got to be something in your code that's causing what you're seeing.

Alan

>Hi Viv. Thanks for the response.
>
>I see what you're saying, but I don't think that's the problem, though. I realize that the mousepointer is a property of an object. It was probably a misnomer to mention that I move the mousepointer. I realize that, if I set the mousepointer for some of the objects on the form and not all, that the mousepointer would change as I move around the form. That's not the issue.
>
>Consider this:
>I set the mousepointer property to an hourglass for the form, which means that, when I drag the cursor around the form, the cursor should be an hourglass - at least when the cursor is only over the form and not another object. In fact, what happens is the mousepointer does change to an hourglass. Then, I move the cursor to a point where it is only over the form (the cursor is still an hourglass.) I leave the pointer sit there and, after a second or two, it changes back to the default cursor.
>
>Now, you would THINK that there is something in my code that is changing it back, but as best I can tell, there isn't. There is code at the very end of the procedure to set it back, but this is occurring while the procedure is still running and before that code runs.
>
>I've been searching through my code to try to find events that might be firing in the background (even though I'm not aware of it) that could possibly affect the mousepointer. But the fact is, I have very few places in my code at all that deal with the mousepointer at all right now. I was in the process of retro-fitting the code to handle the mousepointer in a fashion that is common to other applications. The only other places in my code that touch the mousepointer at the moment are not executed while this procedure is running.
>
>I was really interested if anyone knew of any situations when FoxPro itself intervenes and resets the MousePointer - or if there was any kind of glitch that anyone is aware of. I just want to cover all of the bases, because the solution to this particular problem has been more than a little elusive.