• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 284
  • Last Modified:

splitting access database then rejoining it shrinks database size

hey guys, i've got an access database and it's 30MB after compacting and repairing.

so i split it and i get BE 17MB and front end 2MB (both FE and BE compacted and repaired)

1) how come it shrinks?

then i delete all the linked tables in the FE and then import the tables from the BE. i get 19 MB after compacting and repairing

2) how come it's still 19MB whereas the original database is 30MB after compacting and repairing? seems like splitting is necessary to positively shrink the database.

3) if i just delete all the linked tables from the FE and import all the tables from the BE, is that the right way of merging my FE and BE again? by using this simplistic way did i miss out anything? thanks guys!!

edit: sorry guys dumb question, after some searching, i realised there was missing data which contributed to the database shrinking. but could yall help me answer question 3? what's the right way of merging a split database? thanks!
0
developingprogrammer
Asked:
developingprogrammer
3 Solutions
 
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
3). Yes - pretty much the way you would 'merging'.

However, note that ... almost all professional Access databases employ the split configuration - for a multitude of good reasons.

mx
0
 
mbizupCommented:
<<
almost all professional Access databases employ the split configuration - for a multitude of good reasons.
>>

Agree with MX about that.  

There is no reason to re-combine your database, and a multitude of good reasons to keep it split - even if it is just going to reside on a single system.

Simply copy your back-end to a folder on your local machine and use the linked table manager to point to the file that you have copied locally.
0
 
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
<<1) how come it shrinks?>>

 There are a number of things that don't get exported/imported to another DB.  One is compiled VBA code.  Another is query execution plans.   These things won't be created until you use the DB, so at first it will appear smaller, but very quickly it will balloon up to the size you had before.

 Records in tables are also re-organized and you might get a slightly better fill factor on data pages as a result of that.
 

 and ditto on splitting.  Unless it's a single user situation.  Even then however, I would always split as often it turns into a multi-user situation at some point.

Jim.
0
 
developingprogrammerAuthor Commented:
fantastic guys, thanks for your help!!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now