Hi John,

I am fortunate to have two major clients who could give a rat's ass about what tool(s) I use to get the job done - to them, results are what is important. These are the types of clients I seek, without which, I wouldn't see any reason to continue using VFP.

This is not to say that VFP is best suited for every project (because it's not), but I think you would agree that we can get alot more mileage out of it if certain decision makers would just let us do our job.

For example, one of my clients (a national real estate concern) has absolutely no communication with MS or any of its marketing / consulting entities. They do not waste their time. If they want a property built, they hire a contractor and they do not tell the contactor what tools to use - that is the contractors job - they just want the buildings built.

This VFP vs VB vs Delphi vs WHATEVER is nothing but crap - it always has been and always will be. However, it's not currently perceived that way and I know I don't have to tell you why.

Recent events have shed some hope that future potential clients will start empowering the contractor instead of the Tool_Maker. This is the way it should be in the first place. Ah, but the Tool_Maker is much too greedy to allow this to happen. The Tool_Maker will be successful in the short-run, but in a free market economy, all markets eventually clear.

Eventually, Resistance May Not Be Futile.



>Which is fine by me. We have a great niche... Lets ride it for as long as we can... It will be our little secret.
>