John,

I believe your main problem is you denigrate VFP instead of selling VB. I agree that VB is often a better tool than VFP but it does n7ot that it cannot be done with either tool. The reality is that some people are much more productive with a particular tool and it's certainly something to keep in mind when you are managing a project and your ass is on the line.

One of the company I worked for had four versions of a product (VB, VFP, PowerBuilder, UNIFACE), never mind that were four different versions because they were more interested in selling services instead of products. We developed the second version with a VFP front-end because (1) it supported inheritance, (2) it's easier than PowerBuilder (which was the tool I wanted to use). The product was developed within schedule and generates over $5,000,000 in annual sales and maintaince contracts. Do I believe VFP was the best tool for the job? NO, I know PowerBuilder was a much better tool for this particular product. Did I go against my programmers' wishes? NO, because I did not want to lower morale which was at all-time high. Was this the right decision? YES, you can't argue with success. Do I think we could have done a better product with PowerBuilder? YES, but at a risk. Neither me nor the owners of the company were willing to take that risk. I know that I could have trained all the programmers in any language but I did not want to have programmers writing as their first PowerBuilder application, a distributed application involving 250+ tables.

I love VFP and I spend about 30% of my time working with it (which is about the same as VB and VBA combined). I also work with non-Microsoft tool (PowerBuilder, UNIFACE, FORTE) and I don't see why I, or anyone for that matter, should restrict theselves to one tool...

I don't mind when you write what you can do in VB (some of it I even find interesting), but please tone down when speaking about what VFP cannot do (someone else can often a good solution to circumvent those problems).

My $0.02 worth.

Daniel