Results 1 to 9 of 9
  1. #1
    2 Star Lounger
    Join Date
    Aug 2001
    Posts
    116
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Front End DB Size (Access 2000)

    Ok, I've created my DB. I've split it into a Front End and Back End. There is hardly any data in the back end, but what I am curious about is the Front End - it is around 19 MB in size! That's after compacting. Isn't this going to affect the performance of the DB in the end?

    TIA

  2. #2
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,623
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: Front End DB Size (Access 2000)

    That is extraordinarily large for something that has only queries, forms, reports and code. The largest I've ever seen was around 14MB, and it contained 600+ queries, 150+ forms, 100 reports, and many large modules. Have you tried importing everything into a empty database?
    Wendell

  3. #3
    2 Star Lounger
    Join Date
    Aug 2001
    Posts
    116
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Front End DB Size (Access 2000)

    No, I haven't tried that - but I'm going to. I did try making into an MDE file, this brought the size down to 6MB. That seems a more reasonable size. Any drawbacks (other than having to keep a copy of the .mdb file) to an MDE?

    TIA

  4. #4
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Front End DB Size (Access 2000)

    The main drawback to an MDE is that you can't change any object designs in it and all the code is now compiled and unreachable. Also, if you references get broken in an MDE, they won't resolve themselves as they will with an MDB. Unlike Wendell, I customarily see very large front ends. Our commercial apps run over 35Mb for the front ends and that's fully compacted. One thing to check is whether you have turned off Name Autocorrect in your FE MDB. That keeps a log of changes and it can cause the database to bloat very rapidly. Importing the objects into a new database leaves behind the temporary objects created in the old database as you have run queries, built tables, created and modified forms and reports and, run reports, and manipulated code. Access 2000 and later doesn't clean up after itself as well as might be desired, so you can lose a lot of size by just importing into a new database. If you do, though, make sure to set your references manually after you import everything, because the defaults aren't likely to be the right ones.
    Charlotte

  5. #5
    2 Star Lounger
    Join Date
    Aug 2001
    Posts
    116
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Front End DB Size (Access 2000)

    Importing everything also brought the size down to 6Mb, but as soon as I added to a form it added 1Mb. So I'm turning Name Autocorrect off. I gather that I have to reexport everthing all over again to lose the extra Mb. Arrgh! Oh well, tomorrow....
    BTW - the FE was at 53Mb <fall over faint> when I started this quest to bring down the size.

  6. #6
    Platinum Lounger
    Join Date
    Dec 2001
    Location
    Melbourne, Australia
    Posts
    4,594
    Thanks
    0
    Thanked 27 Times in 27 Posts

    Re: Front End DB Size (Access 2000)

    Has this got anything to do with database bloat and the SPn level you are up to. I remember in the early days of A2k that database bloat was a problem??

  7. #7
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Front End DB Size (Access 2000)

    I'm not really surprised. Access 2000 and 2002 will grow by at least 1 Mb if you just open the database look at a form and close it again. There are upper limits to that kind of bloat, but it does take people by surprise at first. It's one of the reasons the later versions include the Compact On Close option. <img src=/S/evilgrin.gif border=0 alt=evilgrin width=15 height=15>
    Charlotte

  8. #8
    4 Star Lounger SteveH's Avatar
    Join Date
    Jan 2001
    Location
    Chelsea, Gtr London, United Kingdom
    Posts
    587
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Front End DB Size (Access 2000)

    Try this article about the Decompile switch.
    Decompiling has a marked effect on database size and can help remove potential corruption. Just make sure that you Back Up before doing this!
    Steve H
    IT Lecturer/Access Developer
    O2K SR3/O2010; Win7Pro

  9. #9
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Front End DB Size (Access 2000)

    Decompile is very useful but it doesn't *keep* the growth down, it just helps get rid of some of the garbage when you compact after a decompile.
    Charlotte

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •