Mike,

>That interview was nearly two years ago and a lot has changed since then.

That's true, but my point in mentioning it was that YAG was saying back then that the .NET Data team and the VFP team were both part of a virtual team whose members would flex their time one way or the other depending on the needs of the moment. VFP release ramping up, more time on VFP. In between releases, more time on .NET, etc...

>It's possible I was misinformed and Calvin is not as "gone" from the VFP group as the person stated. The way it was said to me was that he has moved to the .NET data group, not that he is on loan to them and is expected back on the VFP team.

The way YAG was managing the data resource people, Calvin was already on the .NET data group back then because they were considered part of the same group.

The same set of facts can be stated in ways that lead to vastly different conclusions. Someone who is emphasizing that the VFP team is dissipating might say "he has moved". Someone who is emphasizing that VFP development continues might say "he is also working with".

There is no mistaking that some key players have moved on to other things or have left the company. But let's not assume that those facts mean that everyone has moved on... that's not accurate.

Another point to ponder... as long as VFP is being officially supported by Microsoft (until 2015 at the moment), SOMEONE is going to be dealing with customer bug reports, especially those that come through free or paid support incidents. The support people are the front line of checking out bug reports or problem scenarios in those cases, but SOMEONE who knows the internals inside and out will often have to get involved, as indicated on Calvin's blog entries.