Ah, but that brings it back to the issue of QofQ being a bottleneck. Doing a QofQ per row that we want to keep is less efficient than doing a number of OR statements inside the QofQ.
> There may be no QueryDeleteRow() in CF, but I find that I can easily > "make" > that functionality by doing a QofQ on the query and just not select that > row > (ie... SELECT * FROM [query] where ID != [id]). > > ....................... > Ben Nadel > www.bennadel.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:238614 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
