>I don't like to put code in the Activate event if I can avoid it because it makes debugging a pain.

There's some truth to that, sine the page Activate gets fired when:

1) Page 1 Activate gets fired on form load.
2) Any page Activate may be "incidentally" fired when a form method, for example, is called when on a page. This is a typical problem.

So, the choices are:

1) Use Click (but has drawback of no Refresh when user tabs pages)
2) Use a pageframe or form property to determine when Activate gets run.
3) Let it run an extra time occasionally. Often there's no harm in it.
4) Do something fancier like David suggested.

Most of my PFs are so busy that I wouldn't dream of trying to refresh all of them at once, though. In fact, that was one of the first lessons about performance problems learned back in vfp3. So I use one of the above 4 ideas, often #3 is fine, maybe with a #2 to help during design phase if needed.