The group I'm leaving hasn't been told to abandon VFP/FP for another tool. If the current redesign effort was in full swing a year ago I believe we would have been hit with that. We were able to demonstrate a clear advantage to sticking with VFP in the short term, and the benefits of using it as a front end as SQL Server comes on line in our group. For us it makes sense because we are doing all order processing/fulfillment tasks. The group I'm moving to allows VFP for personal tools only. They won't allow us to deploy it to end users. This decision was made at a director's level. The manager there is actually an old FoxPro programmer who still thinks VFP is a good choice for certain projects. The director looks at the advertising and all he sees is VB/Access/SQL Server. His mind is made up.

Scott

>I have about the same problem where I work. We can only use software that are on the approved list of the client. I was glad to see that VS was on the approved list, until I noticed the asterix beside it. Looking down for the meaning of the asterix, I saw this: "Except for VFP and VJ++".
>
>We are currently working in Foxpro Windows and VFP in my department, but it's tolerated only because we developped the software before they put up the rule. The product is dying slowly, the upper management seem to have forgotten about it and is not allowing any further enhancement on it.
>