[AccessD] Form corruption

Janet

1) Steve is soooooooooooooooooooooo going to hear that "out-house 
consultant" line :)

2) Max has a beautiful little Access app called "EatBloat" which I believe 
is in version 4.1 at the moment ...it takes everything in your mdb and 
exports it to text files and then builds a new mdb using the exported text 
files from the old one:
    a) ime I've never had a fe corruption issue that "EatBloat" couldn't fix
    b) better yet, as its name implies, it eats all that bloat in your mdb

3) I can e you my copy but better yet would be for Max to send you his 
latest ...he did have a dl point at one time but I'm too old to recall it 
and too short-tempered these days to look for it :)

William

--------------------------------------------------
From: "Janet Erbach" <jerbach at gmail.com>
Sent: Friday, May 01, 2009 3:18 PM
To: "Access Developers discussion and problem solving" 
<accessd at databaseadvisors.com>
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
>