>>>>I disagree... It was his job. If you use that logic, then the original development team in Perrysburg needs to be included also..
>>
>>Baloney. Calvin went above and beyond what his normal job was. Nobody else was pushing vfp into more modern uses since Microsoft wanted to limit VFP so as not to compete with .NET. Just look at his own blogs and presentations.
>
>Amen to that. Calvin's blog was gold. I said WAS since he no longer seems to blog about VFP. Can't blame him for that since he's now turned to the .NET side but back in the day, I couldn't wait for him to write something. I miss that actually.

Me too. Some of his blog entries were pure intellectual curiosity. (Others were pure practicality, and later he was in a close to unique position to implement them in the product). Before blogging he might get wondering about something, then he approached it like a scientist. Rigorous. His father was a professor at Case Western. (For the benefit of those who don't know it, it is one of the leading launching pads of engineers in the U.S. As is MIT, Calvin's own alma mater). The acorn doesn't fall for from the tree.