>>Anybody else noticed the new partially documented and unimplemented property in VFP7?
>>_VFP.LanguageOptions
>>1 = Strict MemVar declaration required.
>>Interesting. I wonder if this will make it to the release version.

---

Woo hoo !! A new way to generate run-time errors! This would have been much better as a compile-time option. IMO the VFP compiler is way too forgiving, and it is about time the VFP team tightened things up. I remember that in Clipper a sucessful compile took you most of the way to the target. A successful compile in VFP means almost nothing.
I guess we won't need EXTERNAL anymore!