That was just an example to explain the difference between the debuggers and where vs2008 debugger is lacking.



>Hi Tracy,
>
>nothing should alter a forms (aka objects) property outside the objects code. This is called encapsulation... (^.~)
>
>Agnes
>>>This is was stops me from moving to .NET (o.o)
>>
>>I'm working about 65%/35% Now (Net/VFP). There are a lot of things I like about dotnet. Too many to list. However, I do have one pet peeve which bugs me almost daily and it has nothing to do with data handling. It is in the debugger. In Fox, if I create a public reference to a form so that a form named myform could be visible app wide (e.g. omyform), I can put a break on one of the form's properties and whenever the value of that form property changes, app wide, it will break so I can trace it and see where in code caused the value to change. In dotnet, that is not possible. You can put conditional breaks at locations, but those conditions won't apply elsewhere. I've searched everywhere to see how to do it in dotnet and asked everywhere I could think of online to no avail. Everwhere keeps pointing me to the conditional break at a specific location, which is NOT the same thing. That feature in VFP makes troubleshooting and stepping through code (when different tiers or layers in a foundation may make the value change) so much faster.