>George,
>
>Second thoughts...
>
>The way my apps are working now the DE is so basically simple I don't have much need for a subclassed DE, the only thing I ever do is go set the BufferMode of the cursors, set the InitialSelected alias and the order for the parent table. I don't relations in there anymore since switching to parm-views for child tables. When I drag a field out of the PM onto a form what gets put in the DE works as is except for those above 3 properties. And if I were much lazier I'd write a builder to set them. *s*
>
>Now this isn't to say that all environments can work like this so I still support the ability to subclass and substitute DEs visually.

Geez, David, I'm glad I waited a minute before replying to the first.:-)

Part of my problem relates directly back to the DataEnvironment (if you could call it that) with 2.x. The code generated by GENSCRN was redundant, and would put you into a seemingly endless succession of errors (because of its placement). As a result, I developed of a way of overcoming these shortcomings (Including functions named OpenTables, and CloseTables). Maybe I'm just prejudiced against relating the DE to the form/report.

I just think we'd all find a great deal of benefit from being able to have it avaialble (both in design and runtime) as an independent object.

Thanks for the feedback. BTW, you ever play around with that app I sent?