Gary Kjos
garykjos at gmail.com
Fri May 1 15:14:20 CDT 2009
Hi Janet, It is my understanding that database corruption is most often caused by network or other hardware issues. If you are working off a network drive you might be having network issues or if you are working locally then you might want to do some hard drive diagnostics to make sure you are not walking the edge before a failure. What version of Access are you using and what version format is the database stored in? I have heard that A2003 database format had an issue that tended to cause bloat. I've continued to always use A2K format for my databases that I update in either A2002 or A2003 versions. I can't remember the last time I ever had a corruption incident but I am mostly doing data extraction from external ODBC databases and then doing quieries over those which are exported to Excel mostly. I don't create a lot of forms or other objects and very little VBA code. Here is an interesting article on Access Database Corruption. http://www.everythingaccess.com/tutorials.asp?ID=Access-Database-Corruption-Repair-Guide Good luck with it. GK On Fri, May 1, 2009 at 2:18 PM, Janet Erbach <jerbach at gmail.com> wrote: > Hello all - > > We manage our order processing/shipping/product inventory using an access > database application developed by some guys in Pennsylvania. I have created > a dozen custom functions within this app that have allowed me to do things > that the original app didn't include. But form corruption sneaks up on me > far more frequently than seems normal. > > It seems to happen most when I've copied a form that I already created and > use that as the starting point for a new form. I'll notice that my response > time starts to seriously degrade - I click on an object and it's seconds > before I can move it or edit it. I'll save the form and my screen will go > blank while it saves, which takes longer than normal. When that starts to > happen I'll compact and repair my database and re-compile all my code just > to clean things up...but it doesn't seem to help. Finally it gets to the > point where I'll try to open the form in design mode and get one of two > behaviors: 1) a message box saying there aren't enough system resources to > complete the operation or 2) NOTHING HAPPENS - the form won't run, won't > open - nothing. > > Is there something I can do to salvage these corrupt items? Should I not be > using a copy of a form as the basis for a new one? Could it be related to > bloat? I'm making these changes in the front end database on my PC...The > front end on the other pcs here are usually around 55 MB, but on mine it > bloats up to around 290 - and even after compact/repair it only shrinks to > about 170. Granted, I have a few objects, forms, and tables that are not > installed on the other front ends - but it seems like my front end shouldn't > be THAT much heftier! > > Any suggestions? > > > Janet Erbach > IT Administrator > Natural Healthy Concepts > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > -- Gary Kjos garykjos at gmail.com