>Regarding DODEFAULT()
>
>I attended a lecture held by Drew Speedie, ( hope that last name
>is spelled right ) Drew said that the DODEFAULT is not always
>to be trusted. There are times it will not call the function
>that you want it to call. Granted the model he was showing
>where this function failed was much more complicated. His
>suggestion was to get familiar with the subclassing syntax
>and call the functions directly ( eg. txtbtns::Save() ).
>
>
>Dan

Dan, this is true if your class hierarchy isn't in a direct parent/child line from the original VFP to your final class. This is can be the case when you make a container of sub-classed items and then sub-class the container. I've found that with VERY few exceptions I am better off planning my classes so there are no 'zigzags' in the class hierarchy. Then dodefault() works fine.

Barbara P. (the OTHER Barbara)