>Hi folks,
>
>I would just like to offer my thanks to all the people that have helped me over the last four months, particularly Sergey Berezniker and Mark Casland.
>
>The community spirit here is great. I would have gone mad without it. The people I work with don't really understand VFP, they just use it.
>
>My boss told me some time ago that I should learn to love VFP (like in a arranged marriage), but unfortunatelly I have gone the other way. VFP really needs to be completely re-written; it has far too many ways of doing the same thing and there are too many obvious compromises. I also suspect that VFP has a better future outside MS. It's quite obvious it's only interested in VFP and the VFP community when VFP has some technology that it wants to nick for VB or C.
>
>I'm off to re-acquaint myself with Delphi.
I believe both VFP and Delphi are great tools for developing applications. Some things about Delphi I like a lot, including: better object-orientation (VFP still doesn't have this for menus and reports), small executables, more checking done at compilation, lots of built-in controls.
However, my knowledge is superficial, and I invested too much time in learning VFP already, so the switch wouldn't be easy for me. This situation might be different for you.
OTOH, I assume Delphi has its own share of problems and required workarounds - this is difficult to avoid with a complex programming language.
Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)