>>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.
>> .
>
>No. Strong typing is implemented in VFP 7 for Intellisense and type library generation only. You can do the following:
>
>local nCount as integer
>nCount = 2
>
>There is nothing to prevent you from assigning .F. to nCount later in your code. However, the cool thing is if you do something like the following:
>
>local oWord as Word.Application
>oWord = createobject('WOrd.Application')
>
>When you type oWord., you will get a complete list of available PEMs associated with the Word object. This makes for far greater productivity when accessing object hierarchy.
>
>HTH.

Let's also not forget the new _VFP.LanguageOptions setting that enforces the declaration of all memvars. Sort of like VB's Option Explicit.