Results 1 to 3 of 3
  1. #1
    Join Date
    Feb 2002
    Posts
    108

    Unanswered: Database Shrunk about 80%

    I have been having strange crashes while using my database. I read here that sometimes importing all objects into new blank database will help with some problems, so tried it for kicks (yeah I know, get a life huh). When I did, and then started to compile, it found numberous errors in code that it never found before. But biggest diff was the new database is about 80% smaller, but seems to run much slower.

    Any ideas ? Is this normal to shrink this much ? Why should it run slower ?

  2. #2
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    No idea why it should run slower, but it is a weird way of doing a compact and repair and so if you haven't done that before, the reduction in size is expected.

    It should run faster though.
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  3. #3
    Join Date
    Sep 2006
    Location
    Surrey, UK
    Posts
    995
    Provided Answers: 2
    It might be that various indices got dropped or rebuilt when you migrated the rest of the objects. Indices are usually the objects to bloat the fastest and take up more space than you would believe possible!

Posting Permissions

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