>>I know that most of you are not going to like this, I didn't like it either, but I had to tell a client to go with Delphi.
>
>I often tell clients that their needs are better served by other products and I don't see this as a bad thing at all. Delphi is faster at screen IO and that kind of stuff and VC++ can be even faster than Delphi. If the app requires that speed in those places then the clinet is best served by using those platforms for development.
>
>However, at raw data processing speed, which is where most of my work is, the fox is still the fastest. Although even there others are catching up. I don't thnk this is so much fox getting slower as it is others getting faster.

Jim is perfectly correct with this.
If the purpose of the program is more graphical then database
driven, VFP is not the product to use. Anyone would be doing
a client a disservice by recommending it. Delphi would be better.

If the project is a database (without pictures), why use a product
like Delphi. It works purely with ODBC which is a dog except
for fetching data on the backend. Power Builder's downside
has always been database speed because it uses ODBC.

How many people build their databases using Excel or 123?
Yes it can do it ... but when the spreadsheet can't do something,
it's not the spreadsheets fault ... it wasn't made to be anything
but a small memory resident database.

It would be better to compare Delphi with Visual Basic,
not Visual Foxpro. (Although I wish VB & VFP would merge.)