>Justin-
>
>PMFJI-
>
>>Its the ONLY way. Since this actually is more work than not using WITH...ENDWITH, I don't even bother using it any more. Hopefully the can fix this bug in VFP 8???????
>
>I agree that it's a bother intellisense doesn't work in WITH/ENDWITH blocks. It doesn't surprise me, though, since our variables, unlike in VB don't actually exist during development. So, it's always seemed to me that the only way for MS to give us this capability is to continually parse our code in memory and store what might be an object in a block.
>
>I have no idea if it's feasible from their point-of-view. In my opinion it's not a show stopper and I'd prefer that the IDE not take up any more memory footprint than necessary. It's not a show stopper because I don't write WITH/ENDWITH blocks until code is tested. And the reason to use them is not just for developer convenience, which is of arguable value anyway, but for readability and for performance. Both of which make the trivial work of reformatting code to use WITH/ENDWITH worthwhile, in my experience. YMMV.
>
>That said, I'm sure could be addicted to it within seconds. *g*

I do not know if VFP 8 will have this, but the "Clipboard" toolbox as they have it in Visual Studio .NET would be neat and helpful here. So you dont have to retype the whole object each time (which you are ofcoz trying to avoid with WITH/ENDWITH) and don't have to rely on Copy/Paste.