Rocky Smolin - Beach Access Software
bchacc at san.rr.com
Tue Jun 3 11:08:41 CDT 2003
If it makes any difference to the thread it is currently single user. If the business takes off it could become multi-user. So I'm glad to know that the Delete/Add field approach has risks in a multi-user environment. Can the risk be eliminated by getting exclusive access to the table before doing the Delete/Add? Rocky ----- Original Message ----- From: Henry Simpson To: accessd at databaseadvisors.com Sent: Tuesday, June 03, 2003 8:34 AM Subject: Re: [AccessD] Update Query - Need to Speed It Up Access is not used exclusively in multi user environments and for those without fancy image processing or signal processing software, it can be used to store and process 30 bit image scans and wav files quite nicely as well as log all kinds of high frequency sampled data. For example, if you want to drop a green cast out of the shadows and don't have photoshop, it's a terrific tool, but you can do it in Access too. If you want to reduce or increase the dynamic range of an audio file that was poorly recorded, all you need to do is apply a scaling factor to some numbers with an update query. My Canon D60 with a 5 megapixel ccd shoots typically 20 megabyte raw images and the Olympus P400 dye sub printer prints 7.7 megapixels on A4 paper. Although Access is not as convenient as photoshop, a tool like Access is just another means to manipulate data that encompasses more than merely Names, addresses and phone numbers. No doubt Rocky wouldn't be messing with 2.5 million records without reason and there is no reason to assume that this would necessarily be a multi user environment. Such an assumption in the face of the information given was improbable. Hen _________________________________________________________________ Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail ------------------------------------------------------------------------------ whew...2.5million records- there's your problem! Have you tried a maketable (create a new one delete the old) setting those fields when you do it? WAG..I know. Other than that how about setting some temporary indices (indexes) on those fields...might help. _D "Things are only free to the extent that you don't pay for them." >From: "Rocky Smolin - Beach Access Software" >Reply-To: accessd at databaseadvisors.com >To: >Subject: [AccessD] Update Query - Need to Speed It Up >Date: Mon, 2 Jun 2003 13:47:27 -0700 > >Dear List: > >I am running an update query on a table with 2,500,000 records and it's taking just a bit too long for the my and the client's liking. >The SQL is: > >UPDATE tblInvoiceDetail SET tblInvoiceDetail.fldInvoiceDetailPPV = """", tblInvoiceDetail.fldInvoiceDetailVariancePercent = 0; > >It's setting one field to blank the other to 0. > >Is there a way to make it run any faster? > > >MTIA, > >Rocky Smolin >Beach Access Software > >_______________________________________________ >AccessD mailing list >AccessD at databaseadvisors.com >http://databaseadvisors.com/mailman/listinfo/accessd >Website: http://www.databaseadvisors.com ------------------------------------------------------------------------------ MSN 8 with e-mail virus protection service: 2 months FREE* ------------------------------------------------------------------------------ _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://databaseadvisors.com/pipermail/accessd/attachments/20030603/6c7acc9e/attachment-0001.html>