I hope you understand that the RELEASE PROCEDURE is a completely separate issue than oSaver going out of scope, which can happen even without a RELEASE PROCEDURE. I'm going to update my previous example to you to reflect that....

oSaver still exists after the RELEASE PROCEDURE, and you can still call oSaver.disablescreensaver after that line.

>Steve
>
>Thanks for your help so far
>
>2 others pointed to the fact that my release was doing the damage - ok it now works but it win't diable a screen saver if it's already started
>
>Colin