>I hope someone has seen this problem. For some reason I can't figure out exiting from a combo box (which is not the last control on my page frame) goes to the Page Activate Event instead of the next control (which should be my state field). I suppose my first queston should be "Is that typical behavior, i.e. does the page activate typically fire after you go to each control?"

Have you checked your tab order? THe page activate DOESN'T fire after each control. It shouldn't fire unless you've left the form (a modal form called,etc.)

>The problem with this sequence for me is that I've been using the Page Activate to select a view (which ties my addresses which are on Page 2 to the name selected on Page 1) and then do a requery(). This works fine when viewing only. But if I change anything in the controls, the requery gives me the message that I have uncommitted changes. Now I'm thinking either a) something peculiar is going on or b) I shouldn't be doing a requery() in the page activate because it fires more often then just clicking on the page frame (which is what I was hoping). But if not there, where?

The Page.Activate() is the usual place. In this case, of course, you don't want to requery while still entering data.

>
>One other thing which may or may not be relevant. I'm not doing anything with SetFocus. I just put the controls I could see in List order sequence (so in my example the problem combobox is a city, which is followed by state.

List Order? I'm not sure what you mean here.