Re: Just uninstalled Delphi 2005 Enterprise

> > I think data-aware components have their use
>
> I've heard too many horror stories and encountered too many nightmare
> creatures arising from them to have even a speck of faith in them :/
> On the scale of bad programming practice, I rank them right with 'goto'
> (the development speed "gains", the maintainance bugs and flexibility
> issues being strikingly similar).
>

Interesting. I've never encountered a development project that chose to NOT
use data-aware controls that didn't have reams and reams of unnecessary
mapping code and corresponding bugs to go with it. The data-aware controls
IMO, though not without problems are a fairly elegant way of producing a
Document-View pattern into a UI. Now mind you I am talking about DataSet
aware and not database aware. I never connect my UI directly to the
database and always use ClientDataSets. Most applications I write this way
have almost Zero code in the UI with all the data handling happening in the
Controller (my version of an MVC / Document View pattern).

Ultimately there has to be a mapping from data to controls. Either you use
a good one out of the box, or build a good one yourself or write a mangled
off the cuff one with no plan.

I'm not saying that a good OPF or other solution might not be better, but in
my experience most projects that don't use data-aware controls because they
are "BAD" end up implementing something far worse.

-Trevor


.

Relevant Pages

  • Re: OOP in database programming - Newbie question
    ... > change database vendors with minimum fuss. ... Certainly data modules help in separation, but many people just put the data ... > Tell me why data-aware controls limit one to a single user system that can ... TeamBUG support for UK-BUG ...
    (borland.public.delphi.non-technical)
  • Re: OOP in database programming - Newbie question
    ... "Joanna Carter " wrote ... If one uses ADO with OLE DB providers you can ... >> change database vendors with minimum fuss. ... > Data-aware controls are only bad if they are connected directly to database ...
    (borland.public.delphi.non-technical)
  • Re: How do you create a data access layer?
    ... > I've read that you really should have a abstracted data layer, ... > decouple database accesses from the rest of your code. ... There are at least two good reasons for decoupling database access from the ... It may be connected to data-aware controls and report ...
    (comp.lang.pascal.delphi.misc)
  • Re: msSQL and ado performance
    ... Do you use data-aware controls or process ... data without visualization? ... As one of the steps you should optimize your database - determnine ...
    (borland.public.delphi.database.ado)
  • Re: OOP in database programming - Newbie question
    ... > your forms to one particular type of database and all the logic that reponds ... > to data changes ends up being written on the forms and means that, ... Tell me why data-aware controls limit one to a single user system that can never ...
    (borland.public.delphi.non-technical)