Rich,

Sorry about the misformatting on my last reply.. miss one little / and everything goes to heck *g*

Sounds like you are on track. VFP is a pretty huge mindset change from FP2.x and it won't all change overnight either *s*. Just remember if it feels like you are doing something the hard way you probably are and there's an easier solution hiding somewhere else.

You can anticipate doing one, two or three major rewrites of your classes over time as you begin to grok the whole O-O philosophy.

>Thank you for the lesson and the logic. As you may have guessed, I used FP DOS for many years. I’m like a kid in a candy store with all the choices. The code in question was on a converted FP DOS form. (And I use the term ‘converted’ very loosely.)
>
>OK, so here’s what I’ve got: keep method code as close to the control as possible. The idea being that the control should be responsible for itself. If the need dictates that the method be called from multiple places, place it in the highest level container that serves all potential users, i.e. if the form has multiple ways to access the method, create a form-level method to do the work.
>
>The CASE statement was dumb. There's no direct connection between it, the actions it triggers or any other control that needs the services of that code. It is plainly obvious to me now.
>
>I’m trying to learn, so your response was exactly what I was looking for. How many stars do you want? ;-)