Tim

>Yes, but EDB is still working in Delphi/BCB as part of the TDataSet
>framework, which hasn't changed much since Delphi 1 (which is actually quite
>a testament to its design, but also partly a testament to Borland dragging
>its feet a little).

I wonder what they'd replace it with?

>No, but that's not what I was referring to. What I was referring to was the
>DatabaseName drop-down for the TEDBTable, TEDBQuery, TEDBStoredProc, and
>TEDBScript components. If you look at the drop-down for the Database
>property of the TEDBDatabase component, you'll notice that it contains the
>Configuration database. That's because the TEDBDatabase.Database property
>is different from the TEDBDatabase.DatabaseName property, which is what is
>referred to in the other components' DatabaseName properties.

Makes sense, I think

Roy Lambert

Roy,

<< I wonder what they'd replace it with? >>

They're already talking about it - something like .NET where you can bind
data to any normal control's property.  IOW, you will no longer need a
TDBEdit version of a TEdit control - you'll just bind a column to the
TEdit.Text property (or whatever).  I believe that is one of the reasons for
the enhanced RTTI - it serves as a foundation for this type of design.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


>They're already talking about it - something like .NET where you can bind
>data to any normal control's property. IOW, you will no longer need a
>TDBEdit version of a TEdit control - you'll just bind a column to the
>TEdit.Text property (or whatever). I believe that is one of the reasons for
>the enhanced RTTI - it serves as a foundation for this type of design.

Wow. Until I pass the unicode barrier (not to likely in the near future) I won't have to bother.

Roy Lambert