>I have found the problem. I added the following at the end of my main page yesterday. This is when the situation started to happen.
>
>

>< SCRIPT>
>< document.Login.Key.focus()>
>< /SCRIPT>
>

>
>So, by default, even if that history is finished, as soon as my process to load the frames is done, the focus is set back to the main page Login.Key field.
>
>I have disabled it for now. Do you know how I can keep this feature but to avoid this situation?

Ok, that explains it...
You could add a focus directive to the onload event of the body of one of the pages in the frameset (the main page, usually). Even after the focus is given to the login form, the focus should be given back to the page in the new window after it loads (put it in the page that takes the longest to load, if any). When you return to the login form, the cursor should be on the box you set it to before also.