What is all that junk in the trunk (DB) ...

[Joe]

Hello All,

I have AC2002 app I have been developing and supporting for over a year.
I have added new features over time. The app is split with a front and
back -end.
Over time the front end mdb has bloated to 15 megs. There is no data here
mind you, just forms, reports and code. It actually has been running very
well.

The other day something got corrupt and although I can open the DB and look
at forms in design mode as soon as I try and look at any code behind a form
or even open a module on its own in the VBA IDE I get the infamous Error
message asking to notify MS and Access crashes.

Compact and repair does not help.

I am now going through the trouble of importing all the objects to a new DB.
This looks to be working and I can now get back into the VBA IDE and see my
code again.

I have custom toolbars. Does anyone know anyway of transferring toolbars
from one DB to a new DB?

CAN ANYONE tell me what is taking up 10 plus megs of space in the MDB file.
I took a copy of the working app from a few days ago(I have learned my
lesson I make backup copy of the days progress every day).
I removed all objects (forms ,reports,code ,etc.) there is nothing in any of
the object windows. I compact and repair it yet I still have a 10 meg mdb.
I know my custom toolbars are hiding in there somewhere. (Why can we not
export those?) This seems like a nasty bug that this incessant bloating
continues. DOES ANYONE KNOW WHY THIS HAPPENS AND HOW TO REALLY COMPACT THE
WASTE SPACE FORM THE MDB.

Thanks,


Joe

 

[James Harbaugh]

Joe,

To import toolbars from another database, go to File -> Get External Data ->
Import... After selecting the database from which you want to import the
toolbars, you will see the Import Objects window. Click on the Options
button on the right and some new check boxes will appear. Please a check in
the Menus and Toolbars check box, clear any other check boxes and click OK.
Your custom toolbars will be imported into the new database.

Regarding the bloating of your front-end database, you should decompile the
database. Here is a link to a good Access resource on decompiling databases
http://www.granite.ab.ca/access/decompile.htm

Hope this helps.

Jim Harbaugh

 

[Guest]

Tools-->Options, select General tab and check Compact on Close. This will do
a compact and repair each time the user closes the database.
This will not solve you corruption problem, but it will stop the bloat.

As to the corruption, you may want to read this site:
http://www.granite.ab.ca/access/decompile.htm
Then try a decompile