>Nope. And it's strong typing, not strict typing. It's not enforced at runtime or design time.
>

And besides, that line of code wouldn't create a variable anyway. It would just "hide" any exisiting instance of variables named "int" or "nCount" from the rest of the follwing code. (okay, I know I'm being picky)

>>I was just reading an overview for the VFP7.0 release and it mentioned the use of strict data types. Now I know that sometimes the MS meaning of a term the remainder of the world's meaning are not always the same, so i ask...
>>
>>does this mean that i could do the following with out error?
>>
>>private int nCount
>>if nCount = 0 && in VFP6 this will cause error because nCount would == .F.
>> .
>> .
>> .
>>
>>
>>- jer