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.

>I just wanted to toss in some experiences I have just run into. I'm switching divisions in my company. The new group I'm going to has people with FoxPro/VFP experience, but we are not being allowed to use the tool. We can write our own utilities for personal use, but anything going to an end user has to be written in Access and VB. Demos have been put together showing that VFP outperforms Access for the types of applications that they are writing, but these have been ignored. The mindset of management is that VB is the way to go because MS does not stand by the VFP product. The lack of any real advertising in comparison fuels this argument. Finally, because VB is promoted so heavily, we can no longer find any experienced VFP programmers for full time work, or graduates who are willing to work with the language. The lack of bodies willing to work with VFP is another driving force to eliminate it as a viable tool in my workplace.
>
>Do you see this trend out in your area? I'm in CT.