Mike,

>I was fixing this problem of two pageframes and hotkeys and discovered another minor issue. ...yes this is terrible interface design...designed by the customer (actually a user group committee)...oh well...

Sounds about like the worst possible design team. *g*

>If you have 2 pageframes on a form and you place hotkeys on their respective pages. The pageframe on which the hotkeys do not work also seems to have an issue with maintaining the current active page setting. i.e. if you have 10 pages (... i know it is a bad idea) on the pageframe on which the hotkey are not working and you first time accessing the pageframe you were to activate page2...then later you manually choose page7 because the hotkeys do not work...on page7 you access a modal form to enter some data....after closing out of the modal form you will notice you are now on page2...not page7...disconcerting to the user! If you were to access page 4 first instead of page2 then you would continually be returned to page4 after exiting a modal form or anything else that takes focus away from the current form....

Are launching the modal form from a control on the page that disappears? Is so something like this might work:

* cmdX.Click()
...
do form modal1
this.parent.parent.ActivePage = this.parent.PageOrder

If that doesn't work you should be able to hook some code into the form.Deactivate() and .Activate() to restore the correct page.

Look at the event logger in the debugger if you want to see what happens when to find the right events to hook to if the above ideas don't pan out.