I'm building a site that logs all submissions from a contact form into an Access database. Every week or so, someone will download the logs into an Excel spreadsheet, which will automatically purge the database.
What should I do to prevent any clashes in the process? Does the Access driver automatically lock the DB, so a form being logged won't vanish if it's INSERTed as the purge is happening? Should I put CFLOCKs around all the queries involved? Should I put a CFLOCK (or CFTRANSACTION) around the download-purge process so nothing disappears in between them? I guess I've never really dealt with DB actions this sweeping - purging hundreds of records at a time - and although I know the above issues apply for most DB-driven apps, the scale of this is just making me want some ideas/pointers on the dangers involved here, and solutions. Any help welcomed! - Gyrus ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
