Results 1 to 7 of 7
  1. #1
    Join Date
    May 2003
    Posts
    4

    Question Unanswered: Bloating problems in Access

    We're having a problem with bloating. Our databse (and we
    don't have access to the code) gets fairly big (1.8G),
    we'll do a compact and repair and it brings it back down
    again (700M). In a day or so it will bloat back up to 1.8
    G. If we do another compact and repair the same cycle
    happens. We're not adding that much new information, it is just ballooning back up to the previous size, as if the compact never ran. Is their a fix for this?

    Thanks,
    Heidi

  2. #2
    Join Date
    May 2003
    Location
    Dallas
    Posts
    817
    Provided Answers: 5
    database bloat - usually from importing text files or make table queries that are overwriten - is any of that the issue?

  3. #3
    Join Date
    May 2003
    Posts
    4

    Bloating

    Unfortunately, no its not. It's almost like it is undoing the compact. It goes back to almost the exact size the database was prior to compacting as soon as it is accessed.

    Any other ideas??? Any feedback is greatly appreciated!

    Originally posted by axsprog
    database bloat - usually from importing text files or make table queries that are overwriten - is any of that the issue?

  4. #4
    Join Date
    May 2003
    Location
    Dallas
    Posts
    817
    Provided Answers: 5
    Create a blank data base

    if you are using a frontend / backend structure you will have to create 2 databases of course

    import all of the objects (the entire db) into the new db

    check the size

    go to the VB editor and compile and save all modules and see if the db compiles. If not the compaction was not really taking place any way - if the compact fails you should get an error

    try this

    if this does not help (the reimportation of the objects) you could use a jetcomp utility - if so then I will send a link or email the file

    But we have to understand why the bloat
    What version - I assume it is 2000 or XP because you said the db was 1.8 gb

    Are there any any images in the application?

    Let me know how this works - I am online most of the day.

  5. #5
    Join Date
    May 2003
    Location
    Dallas
    Posts
    817
    Provided Answers: 5
    Almost forgot - Are you using any ADO or DAO in the application? If so are you closing and "killing" the recorsets?

    If everything is one mdb file you may also try "splitting" the database - seperating the data (tables) from the other objects and linking to the tables - at least that wil drill down to what side of the application this is on - but almost always it resides with the data.

  6. #6
    Join Date
    May 2003
    Posts
    4

    bloating

    The recordsets are being killed.

    Originally posted by axsprog
    Almost forgot - Are you using any ADO or DAO in the application? If so are you closing and "killing" the recorsets?

    If everything is one mdb file you may also try "splitting" the database - seperating the data (tables) from the other objects and linking to the tables - at least that wil drill down to what side of the application this is on - but almost always it resides with the data.

  7. #7
    Join Date
    May 2003
    Location
    Dallas
    Posts
    817
    Provided Answers: 5
    try the import or go with jetcomp
    which version of access

Posting Permissions

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