Paul,

>>I'm not quite sure I follow. Are you saying to use this just as a design aid (if so, I think I understand where you're coming from)?

I think that's what he meant -- eliminate properties that you would count on being there on the next "hit" to the class. Then you'll see what parameters you'd have to pass in to remain stateless and still continue what you were doing.

I'd add also, remember that you can't count on SELECT areas being open, or being positioned on the same RECNO(), etc, so you at the least have to pass in a PK to find the record you were on, and maybe a tag name to then position in the same order you were in, to be able to NEXT navigate, etc.