>>

>> >What? A problem in the dev. product? VFP? Lucien! He said it! :-)
>>
>> I never said VFP was perfect,
>
>Did you not say that the GUI and OOP features were not badly implemented?

again this is a problem with the "visual programming" capabilities of VFP
but anyway VFP's OO does not support everything (e.g. multiple inheritance) and I've said it before - still it is a very good OO implementation


>So you are saying that they do have a bright future :).

u said it - not me :)

>BTW I looked at your DE extraction. It's nice. But to be honest, I'm a little puzzled. Is there
>a difference between using the DE and opening tables in the load event, other than C/S or permanent
>relations?

DEs are more conviniet when desinging pages (esp. in VFP5.0 where drag and drop work better)
there are advantages of having the DE in code (rather having them as a seperate independent object - alas in VFP that means in code) as having more power and being able to use them if u use form classes instead of
Do Form
the DE extractor just helps u have the advantage of DEs as object and to design them with the visual tools

Arnon