>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).
>
Geez Gonz. You taking up mind reading? Thinking of a job with "The Psychic Friends Network"? Exactly, right. Visually design the DE, then you can handle it as needed. Want it in a form at design time? Add it by dropping it on the form or report. Need something at runtime, create it, tweak it, pass it to whatever you're going to need it for. Clean and fast. Progammatically creating it is a pain.