[AccessD] Form Corruption, Part II

Max Wanadoo max.wanadoo at gmail.com
Mon May 11 14:32:42 CDT 2009


Hello Janet,

 

The latest version is here


 

http://www.peoplelinks.co.uk/msaccess/downloads/EatBloatV4-A2003.zip

 

as the name implies, it is written for Access 2003.

 

If you have used it on an MDB which is already corrupted it may not work as
expected.  It does not run any code to correct errors or deficiencies in the
database.  All it does is export objects in text format and re-import  them
again.  That is all it does.  

 

Exporting objects as text strips away any superfluous characters.  If you
open them after export using NotePad or similar you should just see basic
text that makes up that object.

 

The process of importing objects from the text format means that Access runs
code to re-create the object which should be in the correct format for that
type of object.

 

It is not a wonder-program.  Purely a utility to export as text (EAT) which
drops any bloat, particularly that found in modules.

 

If your bloat is caused by, say a memo field then it will have no affect on
that table whatsoever.  That is an issue for tables and the only way I have
found to get rid of memo field bloat is to import the table into another
table and then rename it.  If you export a table as a csv or xls then,
again, it should drop any bloat.  You can then rebuild the table using an
import routine.

 

If you want to use it on a BE then you have to install it on the BE MDB.  It
only imports/exports the objects in the MDB that it is sitting in.

It is correct to link the tables before importing as Queries etc look to
find the tables that they are coded for.

 

Here is the sequence:

BACKUP FIRST

Download and unzip the EatBloat.

Open your FE.  Import the frmEatBloat and run it.  Export your objects.
Close the FE

Make a copy of EatBloat.mdb  Open it.  Run the frmEatBloat and import your
objects that you exported from the FE (after linking in the tables).  Close
and rename the MDB to whatever you want it to be.

Open the FE and do a compact and repair.  Close FE.

The size is now the best you can get from the above.

 

Now do the same on the BE.

 

That is all it can do.

 

Good luck, Janet.

 

Max

 

 

 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Janet Erbach
Sent: 11 May 2009 19:40
To: Access Developers discussion and problem solving
Subject: [AccessD] Form Corruption, Part II

 

Hello, all -

 

I have more questions about dad-blasted form corruption.

 

EAT BLOAT

=============================

I tried using this on my back end database.  I ran the export function,

created a new database, linked all the appropriate tables, imported the ones

that were not linked, and then imported my forms.  At this point my database

was 110 MB (after a compact and repair) ...just as big as it was before I

tried to de-bloat it, and I hadn't even brought in queries, modules, or

reports yet.  I stopped the process, and re-installed my app using the

installer that comes with it.  (54  MB).  After running some custom code I

created to import my customizations, my backend was still only 62 MB.

 

Was I doing something wrong with EatBloat?  It did end up being a worthwhile

exercise for me, because I learned that I can shrink my backend down by

re-installing things from scratch.  But I'd like to know if I was going

about it wrong for future reference.

 

Exporting to Txt

=============================

One of my complex forms went dead on me again today after I made a minor

change to the query source.  I couldn't open it, couldn't run it.  So I

deleted it, imported a back up from a few days ago, and copied all my code

from the 'good' form  into a text file.  I deleted the code and saved the

form;  since this was an embedded form, I did the same thing with the parent

form.  Next I did a compact and repair, then re-opened my detail form to try

once again to make the change to my query source.  Did that, saved it,

copied back my code from the txt files I created and...Kaboom.  It went dead

on me again.

 

What's the proper procedure for using txt files to try and salvage code from

a corrupt form?

 

 

Sorry for being verbose about it.  I really would like to get the demons out

of my form if I can without having to re-build it from scratch...

 

Janet Erbach

Natural Healthy Concepts

-- 

AccessD mailing list

AccessD at databaseadvisors.com

http://databaseadvisors.com/mailman/listinfo/accessd

Website: http://www.databaseadvisors.com




More information about the AccessD mailing list