Do we still need a recordset even for a query returning only a single value?

[prabha_friend]

For Queries like this:

SELECT Sum(Errors.Error_Count) AS Errors
FROM Countries INNER JOIN (Error_Types INNER JOIN ((Processes INNER JOIN Countries_Processes ON Processes.Process_ID = Countries_Processes.Process) INNER JOIN Errors ON Countries_Processes.Country_Process_ID = Errors.Error_Country_Process) ON Error_Types.Error_Type_Id = Errors.Error_Type) ON Countries.Country_ID = Countries_Processes.Country
GROUP BY Errors.Error_Date, Error_Types.Error_Type_Name, Countries.Country_Code, Processes.Process_Name
HAVING (((Errors.Error_Date)=#8/1/2014#) AND ((Error_Types.Error_Type_Name)="Internal") AND ((Countries.Country_Code)='AU') AND ((Processes.Process_Name)='Agents'));

 

[pr2-eugin]

It could use Domain functions instead. Although the few issues with the Domain functions is that they are quiet heavy, less efficient, will struggle when conditions get complicated, JOIN is not possible, cleanup is not actually done.

I would use Recordset any day over Domain function even if it only for one record.