>John,
>
>I couldn't help but reply to your statement "Come on Hank. Well known to whom? 15 foxpro developers that want to stick with fox rather than move ahead?"
>
>This seems a false dichotomy to me. I think the true decision is whether to use the best tool for the job or not. You can program in VFP using the same methodologies that you will use if you switch to .Net. In fact the Fox team practically begged the Fox community to adopt these ideals years ago. If this is true, then what is so bad about VFP? When you think about it, a product like the VFP.Net Compiler will open up the world of .Net to any VFP developer that wants it and conversely will open up the world of VFP to all .Net developers. As a .Net developer if I am called on to maintain a VFP application I can now (Or soon will be able to) compile the VFP application in VB.Net and modify it using what I know. Who knows, VFP may become a sort of prototyping language.
>

I may be misunderstanding you. You aren't saying the eTec compiler generates VB.NET code from VFP code, are you? I thought it generates IL code that can be used alongside IL code generated from VB.NET, C#.NET, etc.