MS Access Database File Size smaller then previous version

[Knick via AccessMonster.com]

I am novice to MS Access Development,
I regularly back my access database every 2, 3 days ...today when I was
going to back my database I saw the access file on the network drive was only

9 MB in size, while the backup files that I had saved few days back were 258

MB in size.

And the network drive is where the database is saved on.
Can anyone suggest something why or how I can track what happend or a way to
compare the backup database with the new database to see where they differ..
how to compare table size or forms size in the 2 database, anyone aware of
any bugs that could cuz a sudden change in the Access Database size?

Appriciate all your input.

Thanks
Knick

--
Knick

Message posted via http://www.accessmonster.com

[Bri]

Knick via AccessMonster.c om wrote:

I am novice to MS Access Development,
I regularly back my access database every 2, 3 days ...today when I was
going to back my database I saw the access file on the network drive was only

9 MB in size, while the backup files that I had saved few days back were 258

MB in size.

And the network drive is where the database is saved on.
Can anyone suggest something why or how I can track what happend or a way to
compare the backup database with the new database to see where they differ..
how to compare table size or forms size in the 2 database, anyone aware of
any bugs that could cuz a sudden change in the Access Database size?

Appriciate all your input.

Thanks
Knick

A database will shrink if you do:
Tools - Database Utilities - Compact Database

This removes temporary objects and deleted objects/records.

The size change you have here is very large. Did the file grow from
around 9 MB up to the 258 MB? Are the tables in their own MDB or are
they with the Forms, Queries and Reports?

To compare the current one to the backup, you could open both up and
look at the record counts of the tables and see if they are comparible.

--
Bri

[Knick via AccessMonster.com]

Bri
I was trying to figure out what happened, if someone tampered with the
existing db... file is on the network drive, the older copies of the db was
258 MB and then today when i was making a back i saw a small file,which was
only 9 MB ... Since it resides on the network their are many who have access
to it... Although I have back copies of it I wanted to see if there was any
way to track when was the last update or modification occure ...

Comparing the two databases backup and the original they both seem to have
the same number of records... Yes the database has forms, Queries, VBA code
Modules and Reports. Tables are with the Form queries and modules

so far I am unable to find any difference...
Thanks for you help
Knick

--
Knick

Message posted via http://www.accessmonster.com

[Bri]

Knick via AccessMonster.c om wrote:

Bri
I was trying to figure out what happened, if someone tampered with the
existing db... file is on the network drive, the older copies of the db was
258 MB and then today when i was making a back i saw a small file,which was
only 9 MB ... Since it resides on the network their are many who have access
to it... Although I have back copies of it I wanted to see if there was any
way to track when was the last update or modification occure ...

Comparing the two databases backup and the original they both seem to have
the same number of records... Yes the database has forms, Queries, VBA code
Modules and Reports. Tables are with the Form queries and modules

so far I am unable to find any difference...
Thanks for you help
Knick

If you can't find any differences then perhaps it is just that someone
compacted the DB. Compacting is a GOOD idea to do regularly. So is
splitting the tables into their own DB. Then you can give each user
their own copy of the application part. This can solve a lot of
potential problems. There is a wizard to help you with doing this. Read
the Help on it first so you understand what is happening.

Your size difference is significant. This could be because of several
reasons; Lots of edits to forms or reports, use of temp tables, embedded
images in forms or reports, lots of table structure modifications, never
been compacted before, etc.

--
Bri