Pascal,

Though I really want the compile to pick out those errors, it sometimes is a PITA.
Have you tried to write some office automation in .NET without knowing which office version the end user is using ??

Strict typing should only be done because it helps the developer, not because the compiler requires to. Sometimes the compiler does not know what to expect since it won't be known until the code runs. This should be made easy and not a pain by having to revert to reflection.

The same applies to untyped datasets. You basically cannot be sure how a dataset looks like, until you receive it from the SQL server. Just as remote views in VFP, typed datasets are not the solution for all problems.

Don't get me wrong. compile time type checking was on my list for VFP10 as I do see that could take a lot of frustration away when making a typo. However forcing it on the compiler level is not the extreme I'm regarding as real progress.

Walter,






>>Thomas:
>>What a concept!!! Try THAT in C# or VB.NET and watch the compiler puke.
>
>Sometimes it's funny how some people find something fantastic while other people find it terrible.
>Your example (what a concept !!!) is one of things I find terrible (in VFP) and fantasticly solved in .net : all the errors which are found by the compiler (watch him puke ...) can't occur at run-time anymore ...