[AccessD] Form corruption

Janet,

  It sounds like you either have some network issues or environment issues
on your workstation.  A little detective work needs to be done there. Ie. Do
others have problems with corruption?  Do you have any problems with other
apps or errors?  Etc.   I would check a couple of basics on your station:

1. MDB's are not being virus scanned.
2. You have plenty of free disk space.
3. The environment variables TMP and TEMP point to valid paths.
4. Clean out all your temp folders.
5. Your up to date on service packs.
6. If your on a laptop, make sure your cabled up rather then using wireless.

  As far as the corruption, really once a DB is corrupt, for the money, the
only thing you should be doing is creating a fresh DB container and
importing everything into it.  Why?

  First importing gives you a sanity check on the all the objects in the
DB;every form, report, table, etc.  If they are corrupt to the point of not
importing, then you really don't want them anyway.

  Second is that other "repair" methods are far from perfect;  a compact and
repair can succeed on a DB and yet it still may be corrupt.  A decompile
from the command line only does one thing; invalidate compiled code.  It
doesn't do or check anything else.

  I hope you are making regular backups, which is your best defense against
corruption, because all the "repair" methods can fail including importing to
a fresh db container.

  BTW, if you do have a form that won't import, one trick to getting it back
is to open it the damaged DB, save it as text, then load that text file in
the new DB.

HTH,
Jim.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Janet Erbach
Sent: Friday, May 01, 2009 3:19 PM
To: Access Developers discussion and problem solving
Subject: [AccessD] Form corruption

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