>>Hi everybody,
>>
>>I recall there were some issues of using return statements within with /endwith blocks. Can you point me out to some related blogs and is it still considered a bad practice to use them?
>>
>>Can they lead to VFP9 crashes (especially since there is ActiveX involved)?
>
>Personally witnessed a returning local var changing datatype in calling function when issued from within with..endwith.
>Uncertain if it was with vfp6 or vfp8 libs.
>After that having only single return statement was given higher priority and a simple code scanner to find returns inside with was written, run directly after next release with manual fixes.
>
>With.. Endwith changed to local temp references whenever I encounter it, as shortened object resolution can be beneficial for perf: get managment approval in advance and schedule such sessions directly for work start or after extended breaks.
>
>Side benefit is code easier to read by having a well named temp reference instead of a dot for which the origin might be 2 screens above.

Yes.
With ... Endwith is a feature I never pined for when I switched to .NET
.NET's awesome intellisense more than compensates for any additional typing.