Steve,

That's kind of a red flag situations. Some hard design questions to think about:

1) "Why don't you want to run the code there?"

2) Skipping a level to call the ParentClass is generally frowned upon it's a sign functionality hasn't been put where it properly belongs.

3) The button shouldn't know any of the details about the class tree of the form. The button should only talk to the form object and let the form deal with it's inherited code.

Refresh() is meant to handle updating of the controls when the record changes.

>Sorry, I wasn't clear enough in my original message. The Refresh() method of my form contains code. When I click my command button, I only want to refresh my form, I do not want to execute the code in the refresh method. That is why I am trying to run code one step further up the tree. If I could test for this situation, I would put an IF condition..DODEFAULT() in the Refresh(), but this is very difficult. Therefore I am trying to access that default behaviour from my command button.