>As others have said, VFP is
not a strong typing language. The AS clause is merely for IntelliSense and for documentation purposes (and for some COM specific things like Craig mentionned).
>
>Some will say that's a strong point for VFP because of it's flexibility, but for me, it's a disadvantage. You have a greater chance of creating bugs and the compiler won't catch them.
I agree. Up until now I thought it added some type safety to my code.
>
>>I've been happily using what I thought was strong variable typing in VFP9 since it was released.
>>
>>Today I just happened to assign a numeric value to a string variable (declared AS STRING) and nothing happened. For some reason that really got my interest and I looked in the help, and lo and behold strong typing in VFP9 doesn't do anything except apparently kick in intellisense during coding and make developers think strong typing actually exists in VFP..??
>>
>>Here I've been touting strong typing as one of the selling points for VFP9 development.
>>
>>Am I missing something?
>>
>>Try assigning the wrong data type to something in a .NET language - strong typing!
____________________________________
Don't Tread on Me
Overthrow the federal government NOW!
____________________________________