I'm losing focus after my last control so that I somehow end up at the Page Activate. The problem with this behavior is that I'm in the middle of an ADD at the time and my Page Activate does a requery(). I don't want that page activate to fire until after I've had the opprotunity to save or cancel the add. I suspect this is because I'm not doing anything about controlling the focus after the last controls (or at all for that matter) and realize I need to do this. My controls are basically in the proper tab order so once I click my mouse in the first control they go through the proper sequence until the end where the problem occurs.

1) I'm using an edit on entry screen so when I go to that page don't know where or whether I should do a set focus (i.e. do I make the assumption they're going to want to edit as opposed to navigate? I'm just looking for some feedback or suggestions on what others do.

2) Do most people put a setfocus in the lostfocus of the last control (for example something that would make a save or cancel the next button selected - something that would prevent focus from going off into the wild blue yonder)?

3) Since all of the controls (including navigation buttons, command buttons, etc.) have a tab order, is there a recommended order, i.e. should I put editable controls first in the tab order or last (again just looking for some feedback).

4) Is the read only or enabled property a factor in tab order, i.e. can a control with enabled = .F. still be tabbed to, and if so, can I prevent this, or do I need to add read only as well?

Thanks in advance for the info.

Sylvia