Curious behavior of Access2000.

F

Frank Martin

I use WindowsXP.

The other day I corrupted my business database by inserting a "me.recalc" in
the wrong field.

I fixed it partially by creating a new blank database and then importing all
the objects, macros & code from the corrupt one, and then fixed it
permanently by removing the "me.recalc" from the wrong field.

But I noticed a strange side effect in that the size of the database is now
11Mb where before it was about 13Mb, and these sizes refer to the compacted
databases.

If anything the database is now faster than before.

Can anyone explain the above results? And should I routinely import all
objects etc over into a new blank database?
 
D

Dirk Goldgar

Frank Martin said:
I use WindowsXP.

The other day I corrupted my business database by inserting a
"me.recalc" in the wrong field.

I fixed it partially by creating a new blank database and then
importing all the objects, macros & code from the corrupt one, and
then fixed it permanently by removing the "me.recalc" from the wrong
field.

But I noticed a strange side effect in that the size of the database
is now 11Mb where before it was about 13Mb, and these sizes refer to
the compacted databases.

If anything the database is now faster than before.

Can anyone explain the above results? And should I routinely import
all objects etc over into a new blank database?
Click to expand...

This is fairly normal behavior. In the course of development, Access
databases accumulate "dead code" and detritus that doesn't go away when
you compact. I don't really know why. Importing all the objects into a
new blank database leave the junk behind, so you end up with a leaner,
meaner database.

I know a number of developers who routinely do just what you suggest,
import all objects periodically into a new blank database while they are
working on a database. This is more problematic, I think, for databases
to which user-level security has been applied.
 
F

Frank Martin

Dirk Goldgar said:
This is fairly normal behavior. In the course of development, Access
databases accumulate "dead code" and detritus that doesn't go away when
you compact. I don't really know why. Importing all the objects into a
new blank database leave the junk behind, so you end up with a leaner,
meaner database.

I know a number of developers who routinely do just what you suggest,
import all objects periodically into a new blank database while they are
working on a database. This is more problematic, I think, for databases
to which user-level security has been applied.

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)
Click to expand...


Well, we live & learn!

Thank you, and I will perform this routine about once /year.

Regards, Frank
 
Top