My biggest problem in this area comes from the Visual MaxFrame foundation. Because it calls so many internal functions a variable can go in and out of scope multiple times as subclassed methods are called.


>< shrug >
>Well, I can't say that I have the same frustration at all...except when it comes to trying to debug stuff thru the activate and deactivate methods. That sucks. What do you mean by "breaks"?
>
>A break on a watchpoint really only makes sense w/i the scope of the variable. One on a form property should work well for the life of the form. Sometimes I will put the break on the _screen forms collection object instead of using thisform for the reason you describe.
>
>>Nancy, I have problems with break/watch points because as the variables go in and out of scope VFP 'breaks'. This can waste a LOT of time if you're working with local variables and calling other methods.