Walter,

>Hi doug,
>
>>I think that there's some good historical reasons why VFP uses tables for a lot of its work. The questions, I suppose now, is whether or not those historical reasons still have as much weight as they did then.
>
>>I do remember thiking to myself just how smart it was to use the internal data engine to drive the product extensions.
>
>This mean you don't believe in data driven applications anymore ?

No, not at all what I meant. I absolutely think that data driven apps are the way to go. I was commenting on the notion that FoxPro itself uses tables and with respect to the idea of two-way developing that another option in addition to what FoxPro already does would help if the development manegers of VFP though two-way was important enough to add.


Personally I'd like to see more enhancements made to make this easier. (for example build a form in a cursor, and run it from that cursor, the same for classes and reports). I also think that the introduction of the COMPILE command is a prove that there is need for such enhancements.
>
>Walter,

You bet! You have essentially put your finger on my basic point - that FoxPro has, from the days of FoxBase itself, has constantly had new features added and options provided. I have full confidence that this process will continue - hence a large part of my optimistic outlook for VFP.