Oops, that wasn't exactly what I meant!

If you are looking to evaluate an expression, i.e. view the value of a variable or property, use the Watch window.

You can also DIM new variables in the command window and call object methods to assign a value to the variable. The value of the variable will then be in the Locals window.

>Good Sir, I'll have you know that by NO MEANS am I an ex-VFPer. <vbg>
>
>VFP for Win32, .NET for web apps—that's what's afoot here :)
>
>So I guess the .NET CW is simply unable to evaluate expressions at design time? If that's the case, what have you found to be the easiest and quickest way to run ad-hoc evaluations?
>
>
>
>>For ex-VFP'ers, the Command Window does seem that useless. I use it mostly as a substitute to editing code in-place while debugging. But there is only so much it can do because .NET is a compiled language.
>>
>>>Yikes! What must they have been thinking? All I can ever get it to do is reply:
>>>
>>>

"The expression cannot be evaluated while in design mode."

>>>
>>>Surely the thing can't be that useless... can it? Has anyone ever had any luck with it?