"Didier Chesto" < w> wrote in
message news:1k7adbzm617af$.1w17dw68ot44w$.. ..
> Op Mon, 25 Jan 2010 21:34:59 -0500 schreef Scott M.:
>
>> How about using ASP .NET and ADO.NET instead of Dreamweaver and Classic
>> ADO,
>
> Totally true. I'm in the process of hiring a professional with the latest
> skills. Until then I try to cope myself with programming techniques I
> learnt in the 80's (I got away with that for too long
)
>
>> where there is no such thing as a RecordSet?
>
> You mean there's no recordset in Classic ADO?
No, the sentence was "How about using ASP .NET and ADO.NET instead of
Dreamweaver and Classic ADO,
where there is no such thing as a RecordSet?" ADO .NET does not have a
Recordset - it's obsolete.
I think you'll find that using COM objects (recordset) in a .NET
application, will actually cause the performance of the application to
degrade. Unless you have a specific reason to be using the recordset, you
shouldn't be using it at all.
-Scott