>What I am trying to achieve, Yousfi, is this - I have a form that shows a lot of information about jobs. You type in the job number, or the invoice number, and the form finds it, and loads all the details. Then it setfocus to the field to post a payment. The user types in the amount and hits TAB, or ENTER, and focus goes back to the field to call up the next job. So the lostfocus of the payment field sets focus to the 'look up the job/invoice number' field again. It is fast and very convenient when they have to post a lot of payments, but every now and then they will need to look up something in the rest of the form, or make a note in an edit box. The problem is that a mouse click registers the same lastkey() value as ENTER button, which will take you to the call up job field again. So in lostfocus I have had to specify TAB and ENTER to go to the lookup field again. DownArrow on the keybord takes them to another empty field, from where they can now click the mouse on the pageframe for details, or the edit boxes for notes, but it isn't professional. It would be professional if they don't need to enter payment to just click on the edit box, or pageframe, and that which is clicked on gets the focus. This is what I am trying to solve...

possible solution

job number [tab] payment [tab] ok-button (default, executed with [enter]) this click sets focus back to job number [and complains if no payment etc]

if user decides to focus outside this loop he has to [tab] or mouse click back in this loop

so there is a fast loop for those who know and the rest will mouse navigate anyway