As far as I know, the strict typing in VFP7 is not strict :)

Strict typing in VFP7 is used to create COM+ components and indicate the type of the parameters that your methods will use. The strict typing will only serve to let other components what your code is expecting.

Inside your code, the strict typing will have no effect. So you can declare a paramters as integer and assign a date to it and VFP won't complain. Yet, whomever needs to use your COM+ component will know that you expect an integer (while in the pass they only knew you expected a variant data type.)



>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