[AccessD] Which Is Faster - DAO or db.Execute?

Gustav Brock Gustav at cactus.dk
Thu Oct 30 12:31:16 CDT 2008


Hi Max

Reading again:

---
In the detail event of a report, I want to set one of the fields in the
underlying recordset to true.  It's an invoicing report and I want to set
the detail record's 'Billed' field to true.  The Billed field is not on the
report - just a convenient time to set the flag.
 
Would it be faster to use db.Execute "Update...Where " or use DAO
rs.FindFirst.  The Where part of the db.Execute and the FindFirst both use
TimeSheetID for the search - a primary key. The table is a linked table - so
no Seek.  The number of detail records per invoice is pretty low - average
10-20.  So, not like it's updating a large number of records. So response
time is not an issue.
---

So you may be right. I recalled it as series of runs of the report where you would need to look up the id of each invoice.
However, it seems to be the invoice lines that should be updated in which case you, of course, only need to look up one invoice id.

Now, what to have in mind here is, that the update will follow the run of a report. Compared to the time this will consume, the time for running the update will be of zero importance, thus I think - in this case - the question of ADO/DAO or SQL is moot.

/gustav


>>> max.wanadoo at gmail.com 30-10-2008 13:31 >>>
So, how does what I posted differ from these two postings below?
I think my posting was entirely within the bounds of the questions being put
back and forth between different people.
Sorry if I got that wrong.
I will drop out of the conversation
Thanks
Max






More information about the AccessD mailing list