GMTA Arnon <g>...

I wrote a visual DE extractor as well and posted it here in April. It's called unDE. Been thinking of writing a visually-designed form extractor if I ever find the time.

You can do a lot of stuff now with a DE object, but I think what George is leading to is a DE that you can visually design in a VCX, subclass it at will, and attach an instance of it to a form or report through a property setting. Make the DE object as flexible and useable as any other container object.

I'll go one better: It'd be super nice to be able to refer to all table and relation attributes in a DE object solely through OOP constructs (collections and the like).



>I use DE objects which I currently store in PRG files (moving to VCXs now)
>there are added benefiets like the ability to sub-class the DE itself
>I also created a tool for VFP5 that extracts the DE from a visually
>designed one
>
>Arnon
>
>
>>
>>I thought it might be interesting to get some feedback on the following.
>>
>>I believe that the DataEnvironment is too closely tied to Forms/Reports.
>What I'd like to see is an independent DE that could be manipulated without
>the need for either a Form or Report. It would especially helpful in
>developing forms that would be more re-usable than they are now.
>>
>>Thoughts? Opinions?