With existing apps, my experience has been that IT departments will not switch to a new development tool unless they have a business need that cannot be met by their existing tool of choice OR they cannot find developers for their tool of choice. The same has held true for developing new apps for the SAME company. Now as for developing new apps for a new company (say a new contract for developers that do contract development) then they may question the tool of choice for the developer. This has been my personal experience, and I have known cases where the company did NOT want to use VFP also. I've also known companies that had apps rewritten in VFP from other even less used development tools like PDI Adept and others.

Tracy

>Fernando
>
>There is a difference between the bespoke (custom) development market and the product market.
>
>If you are selling products, if they are first rate and meet customer need, and if you are a credible business, then the customer will buy. Development tool is way down the list of decision points. I think this is Wayne Myers' experience.
>
>If you are doing custom development, you have an issue that extends beyond VFP. It is most unlikely that bespoke development will proceed at the pace it did through the 90's. Companies with solid win32 apps are not going to queue up to have them rewritten just because a new tool has appeared. If everybody is converging on dotNET and Java/Linux then there is a serious oversupply issue on the horizon.
>
>IMHO contractors need to broaden skills not only to new tools but to whole new roles- say project planning, software architecture, management, web design as opposed to programming, or business analysis. People who used to just program are most likely going to have multiple roles, some technical, some management or creative.
>
>Either that, or contractors should band together to commercialise their best products so they can join the Wayne Myers experience.
>
>Regards
>
>JR