I appreciate what you say about seperating the two. Its the real work class thats causing me troubles. If I understand you, my stupid code example using the do_all_the_real_work_that_page1_needs_done method is OK.
The question then is when you say

I usually use data handling classes just for handling data related to their namesake.

What do you do if you need code that handles data from 2 data handling classes? I can use a has_a relation for simple things but when things get more complex, I'm at a loss as to how to lay it all out.

I'm guess my problem is with basic OO design issues, I'm just looking for some clues as to how to lay it out.