I also don't like forced logoffs. The client uses databases quite intensely and I've alsways worried about damage to fragile tables if open files are involved.

Frankly I sorta still believe my simple process of cpaturing the user password and then forcing a password protection of the screen saver (all via KiXtart) would be a useful tool to achieve my aims.

I didn't intend to retain or record the password and once the KiXtart script concluded, there would be no record of the password being retained.

However - apossible problem (as outlined by MCA) to my thinking is that the screen saver passwords may be retained in plain text within the registry or .INI files.

BTW, management has made all employees sign a legal document relating to the use of the provided electronic communication devices accepting certain "rights" by management to observe non-work related e-mails, personal calls, obscene content mail and web pages, etc.

Michael