>>THe best advertising for VFP is successful, operational products built using it. I get more VFP business from frustrated people having custom Acess and VB solutions who've then seen what similar applications built using VFP were able to do, especially wrt time to deliver the working product from start to finish. A good app written with VFP, that proudly displays the Fox Head rahter than trying to hide it's origins is what brings in people looking for something developed specifically in VFP; I've yet to run into a situation where the client rejected a working solution because the development platform was Fox, unless there were specific technical arguments (such as the ability to deploy on a non-Windows environment platform) which ruled out VFP. THey may hem and haw at VFP as a platform, but once they have something that works in Fox, the demands for another language seem to diminish.
>>
>>
>You get no argument here. I'm a VFP bigot from way back. My concern is that MS's future support of VFP may make their past support look like they had been advertising it on the Super Bowl.
>
>I've just entered into a contract with a company that has a front end done in Delphi talking to MS SQL Server 7. I can pull the data from SQL Server and munge it much faster than Delphi, so they don't care what I use. Someone else showed them some stuff I had done using VFP and Web Connection.

I don't understand the importance of the MS advertisement of FOx on it's use by developers; I have yet to run into a situation where the TV coverage of Delphi or Power Builder generated a lead; the only thing that seems to affect the acceptance of VFP as a platform is the FUD mongers preaching about hopw the end of VFP is upon us, and we must repent our sins and go into the house of God, speaking the one true universal language (which happens to be APL < g,d&rvvf >)