Correction: You cannot generate an error with the LanguageOptions setting, but can cause error output to go to the DEBUG OUTPUT window or to a file set with SET DEBUGOUT TO... It's all in the docs.

>Paul,
>
>You cannot enforce types in VFP, but can generate error output for undeclared variables in VFP7 with this setting:
>

>_VFP.LanguageOptions=1
>

>Look up the topic "LanguageOptions Property" in VFP7 help.
>
>>Is it possible to force VFP to strictly type variables and properties...for instance I can do this:
>>
>>local xyz as number
>>
>>xyz=""
>>
>>and it retains the string. I have to say that I would rather it gave me an error, preferably at design time.