Is there any way to stop a screensave from triggering the lostfocus event on an editline?  We have a program that routinely runs for extended periods without user interaction, and the screensaver usually starts up.  The problem is that the first editline on the form validates the data entered on the lostfocus event, and the screensaver triggers this event when it starts up.  The result is that as soon as the user returns to the computer and moves the mouse, the program tells them that the data entered is invalid.  This is annoying, but hardly a major catastrophe.

   Can I trap the lostfocus event if focus is moving to another application so that the event doesn't get run?  Is there any other way to stop it from firing this event in this instance?

   TIA

        Duane Pekse

        ALDATA Software Management Inc.

        [email protected]

Duane,

There is a way to detect this, but I cannot remember what it is. I had the same problem years ago when I was working with Powerbuilder … I think it would GPF when the screen saver kicked in (if the focus was on a control that had a lost-focus implementation).

What I would suggest is using the Flag parameter in the LOSTFOCUS event to handle this:

Flag can have one of three values:

Cameron Purdy

Revelation Software

View this thread on the forum...