Results 1 to 3 of 3

Thread: Compacting

  1. #1
    Join Date
    Feb 2004

    Unanswered: Compacting

    Can someone tell me if this is going cause a problem.

    We are using an Access based system that has around 10 users and I set up the database so that when it closes it automatically compacts. Trouble is one user may exit the database but the other 9 users could be in it. Will this
    1) Cause issues for the other users in the database if they are still updating dat
    2) Corrupt the database.

    If either of these issues are the case, is there a way of only compatcing the database when the last user has exited the system?


  2. #2
    Join Date
    Oct 2003
    Provided Answers: 1
    . It will not corrupt the DB, because it makes a Temp file and the compaction
    is Ok, will be renamed

    . On exit the application, it will try to compact it, but failed because someone
    else is in the DB, so it will issue only for the user that user and not the others

  3. #3
    Join Date
    May 2004
    The Netherlands
    I am not sure what kind of problems will occur. But what we always do, is separate the application layer (front-end) from the datalayer (back-end). Every user will have his/her own application which has a linked tables to the back-end database. From front-end database it is possible to manage compacting of the back-end database. Separation of these layers will have the advantage when installing an upgrade in the front-end, you can leave the back-end database intact.
    Also it is better to compact the front-end database when it will be closed. Running queries will blow up the front-end database also.
    Last edited by Robje73; 05-26-04 at 07:57.

Posting Permissions

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