>Hi Ken,
>
>Our local technical guy (out of the Microsoft Austin office) is Stephen Fulcher. He has provided developers in this area with many excellent technical sessions and has just recently been promoted to a new (local) position. Stephen is very competent in VB and .NET but needs some VFP familiarization.
>
>An example:
>
>At DevDays last week we were discussing (on the sidelines) the fact that VFP was not part of VS anymore. I made the comment that part of that decision was driven by the developers and Stephen replied that he thought it was because VFP was not an OO language.
>
>Don't get me wrong, Stephen is a great guy and an asset to Microsoft's staff. If you haven't already done so, maybe you guys could circulate some general VFP "required reading" info to reps in the field.
>
>Thanks for your continuing support of VFP.
I'm in the process of making sure Microsoft field offices are much more educated about Visual FoxPro 7.0 and how it fits into Microsoft's .NET strategy, future of VFP, etc. I will be sure to send some information to Stephen to make sure the right message is stated about VFP in the future. This is the exact type of feedback I need to help in my efforts, a short description of the situation/issue with reference so I can take specific actions to correct the problem. There are activiites I'm working on within Microsoft to help prevent mistakes like this in the future, but I always need useful feedback like this when it is needed, thanks.