Stuart McLachlan
stuart at lexacorp.com.pg
Mon Jul 4 04:19:36 CDT 2011
Good point, I didn't think of the confirmation of multiple deletes requiring a temp table. On 4 Jul 2011 at 10:11, Gustav Brock wrote: > Hi William and Stuart > > I don't think that's the reason, but it is similar: Access walks > through the recordset (which may be filtered) and copies all records > to a temp table to hold them in case you - when asked later via the > GUI - choose to undo the operation. Only if you choose to confirm the > deleting of the records, this actually takes place. > > /gustav > > > >>> stuart at lexacorp.com.pg 03-07-2011 23:56 >>> > A SWAG: > Because Access can't tell that all the records are selected. It has to > step through the rows and checking the "selected" attribute. That > means that it can't implement a simple "Delete * From tblA" but has > to specify each of the records separately for deletion. > > -- > Stuart > > On 3 Jul 2011 at 17:23, William Benson (VBACreations. wrote: > > > Why is a query that deletes all records from a table so fast in > > comparison with a manual delete operation on a table that is opened > > in datasheet view? > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >