difference between using a recordset and domain aggregate function...

[mahaMutant]

It seems that like me, many users of access and visitors to this site [1 of the coolest on the web] find the concept of using recordsets mind boggling...
I have a monster of a book [damn expensive it was] but after spending hours trying to "understand" DAO / ADO / recordsets, I still feel I lack a decent understanding of the fundamentals here. Can anyone suggest a good point of clear info on the real difference between the above, the caharacteristics etc...
e.g. a typical scenario: i want to get to a specific record, why exactly would I use a recordset if I can get there with a domain aggregate function? - is it to do with the 'pointer' vs 'sql' ?
or;
I have an extensive database working etc, and looking at the code behind the forms and modules, there is not a single instace of recordsets to be seen anywhere - how come to get to a record - it is constantly suggested here that I use recordsets etc...

Anyone feels like elaborating on this one...
Thanks in advance! ] always a sucker to the greatest lie of all: will only take a minute [

 

[cmmrfrds]

What do you mean by domain aggregate function?

In general, you might need to use a recordset where you cannot solve a problem in SQL in an Access Form or report. Typically an SQL statement will return a resultset to a Form or Report and this is a large part of an Access application but there are time when you need to do some special processing on a resultset that is placed in a recordset. That way you can manipulate the data in VBA code. Also, in an ASP page since there is no recordsource property like in Microsoft Access or VB.