I'm with you. I like VFP, but there are still some BIG holes as far as I'm concerned.

>I'll probably get flamed for this, but this is in the spirit of John Petersen's post at the VBPJ forum...
>
>Everyone points to VFP's OOP as superior to VB's object based approach. But what about VFP's lack of a full component based approach to development, something I've only seen personally in Borland products?
>
>Look at VFP's "Main Window", Report Writer, and Menu Designer. These are left-overs from FPW 2.6! VFP 5.0 should have dropped these and other unnecessary hold-overs from the past to attract new blood to the product.
>
>One can spend a lot of time going through various properties which indicate that they are for backward compatibility. How about giving us a fully component based VFP without all the luggage to support procedural coding practices from the past? Why would anyone want to convert an existing FPW 2.6 or FPD app to VFP? The forms look better in the older Fox versions...
>
>Let me get my fire suit on...