>>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.

Houston,

I think you've got this backward. From the VBScript help on that environment's Option Explict statement.

"If used, the Option Explicit statement must appear in a script before any other statements.

When you use the Option Explicit statement, you must explicitly declare all variables using the Dim, Private, Public, or ReDim statements. If you attempt to use an undeclared variable name, an error occurs.

Tip Use Option Explicit to avoid incorrectly typing the name of an existing variable or to avoid confusion in code where the scope of the variable is not clear."

Not having access to the copy of VFP 7.0 that was distributed at DevCon, I can't say for certain that it's the same in VFP. However, I would say that, if invoked, an undeclared variable will generate an error at compile time.