I have an application originally designed in Access 97 which I recently converted to Access 2000. Some forms have two pages using a pagebreak. Everything worked as expected in Access 97, however since converting to 2000 there now seems to be a problem related to the use of [ObjectName].SetFocus On clicking the Update button I carry out validation to ensure certain fields contains values. if they do not I display a messagebox, set the focus to the appropriate object then exit the sub procedure. Within Access 2000 it now seems that, even though I am solidly on (say) page 2 (as are the objects I am validating) setting the focus to any of these objects now messes up the pages. I end up with page 2 covering only the bottom 25% of the screen with the other 75% taken up by the lower sections of page 1. I can get around the problem by ensuring that before exiting any code within which an [ObjectName].SetFocus has been executed, I do a Me.GoToPage 2 (say). The problem is that it requires many such instances where nothing was required under Access 97 and it causes the form to flicker slightly (using DoCmd.Echo False/True doesn't help) Has anyone come across this problem before? Any suggestions anyone?