Eliot Muir etched the following on virtual vellum:
> I remember years ago getting rather burned by using databound controls in
> Delphi - they just fell over with multiple users and I know Ian
> Farquharson
> & co ended up spending much of their time
> at Profax rewriting chunks of the Delphi data base system.
On one of the "& co" I thought I should explain the profax position.
We use almost 100% data bound controls in the Proafx code and it all works
very nicely now. Initially we experianced three main problems with the out
of box Delphi code:
1. Data bound controls did not provide enough events to provide the control
we needed. This was easily fixed by extending the existing TFieldDataLink
interface to our controls and providing all the events that we wanted.
2. The native Delphi master-detail TTable linking doesn't work efficiently
at all times. This is due to its use of notifications between tables. We
solved this by writing a table management component that drives all of its
controled tables optimally in all cases.
3. We hated BDE. So now we use our own TDataSet replacements that need no
supporting libraries. In this way we have all the features we want, any bugs
are ours and can be hunted down and fixed, and our applications are many
megabytes of disk smaller.
After 5 years working with the data-aware controls I can report that the
design is fundimentally good with only a few obscure niggles. And it it
hadn't existed I would have had to write something equivalent to get data
automatically into, and out of editing controls, because there is no way I
want to write the code to do that many times. The only current enhancement
that would be nice is to be able to replace the entire data-aware area opf
teh code with interfaces that would provide a much cleaner implementation
mechanism.
Cheers, Max.
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
