>Hi George,
>
>I know you have better things to do and I'm sorry but I still don't get it!
>
>When I refer to the screen saver being active I mean actually running. I don't see how the test code can be ran without first de-activating the screen saver.
>Thats why I used a timer. While the timer was counting there was enough time for the screen saver to start running. Then when the timer event fired I could test to see if it was turned off ( as though there was user interaction ).
>
>All your help is greatly appreciated. I think maybe this one may be a lost cause.
>
>Ray

Ray,

I'm at home now, so this response won't be comprehensive, and may not be able to provide an answer. I'll do some checking in the morning. The function determines whether or not a screen saver is available to be run, not if it's already running. So there's a bit of a misunderstanding here.

I'll going to do two things tomorrow (at the office) to see if there's a solution. One is to check around and see if there's a way to determine if a screen saver is already running. The other is to see if there's a programmatic way to stop it. I've a couple of ideas on both, but don't know for sure.

'Til tomorrow.