>>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. I don't think so, for Real Time apps, I still used C or Forth to talk with the components and FPD only for reporting >> 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. VFP uses open standards (ActiveX, ODBC etc.) so so you can always plug VFP or plug into VFP things that are created by other programs and IAC, it is not as if there is no more development of VFP in MS. consider for example that VFP6 will have Active Document capabilities (the ability to instantiate a form as is in an ActiveX enabled browser etc.) that VFP5 doesn't have Arnon