[DUG] Connectionless recordsets

[Jeremy Coulter]

Hi all.

I am in the process of redeveloping an existing application that has reached
the end of its ability to add stuff nicely without breaking other bits of
the code. Admittedly best practice was not always followed :) but its time
to start version 2 of the app.

As part of this I am splitting stuff up into database, business and GUI
layers - on paper at the moment, and a thought occurred to me. In .Net which
I sometime work in, you uses datasets which are basically connectionless,
and I wondered if anyone can think why I would not take a similar approach.
I am using ADO, and at the moment I have a test procedure that calls a
stored proc, then passes back a TADODataset which is not connected to any
database, connectionless, then this procedure "does something" with the
recordset, just looping it and printing stuff to a listbox at the moment.

When its done, it frees the object etc.

Can anyone see anything wrong with this approach? Or things I should be
aware of etc?

 

Thanks, Jeremy

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://listserver.123.net.nz/pipermail/delphi/attachments/20131104/53529e1f/attachment.html