>>I don't argue that VFP is NOT a be all and end all development language, it was never meant to be.
>
>Why not? It could have. FPD was.
>
>
>> VFP is a database management application development language and I still say there is no other language that can rival it for database management.
>
>
>Today. But what about tomorrow when we will have our customers demand us things that can be done easily in VB and not in VFP? And this for no other reason than somebody somewhere decided that the future lies with VB and not with VFP.
>
>
>
>Marc
Marc,

FPD was not the end of all programming languages either, its screen IO could be blown away by a C or C++ program. It didn't handle the visual display of information very well at all. It was overly sensitive to the memory management being used on the machine (try running FPD 2.5 while DPMI memory is in use).

As for tomorrow I expect requests for things like active documents (which we have seen demoed in VFP 6.0 already) tighter intigration with the internet (which is also in VFP 6.0) tighter and fuller support for ActiveX stuff (which has gotten better with every release of VFP).