Results 1 to 4 of 4
  1. #1
    2 Star Lounger
    Join Date
    Jan 2001
    Location
    Portland, Maine, USA
    Posts
    173
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Database Maintenance

    I was wondering if repair and compact should be used on run-time versions of my database? Would each user notice any performace gains? Our database is split with the backend on the server. Should I also be compacting the backend table also?? Thanks to all in advance.

    Jols

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

    Re: Database Maintenance

    If they are truly using a runtime version, compacting the front end may not make much difference unless your application generates make-table and other action queries. In that case, compacting will get rid of the bloat caused by those queries. Compacting the back end will only be necessary if they do a fair amount of deleting of records, since that space will not be recovered otherwise.
    Charlotte

  3. #3
    New Lounger
    Join Date
    Feb 2001
    Location
    Southern U.K.
    Posts
    12
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Database Maintenance

    But I thought compacting and repairing was *essential* to the healthy running of an access database (the back end that is). I have always been lead to believe that your database will eventually corrupt without frequent compact and repairs. Hence the Jetcomp utility?

    Kindest Regards

    Paul <img src=/S/confused.gif border=0 alt=confused width=15 height=20>

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

    Re: Database Maintenance

    It depends on a lot of things. Do you use memo fields in the application? How much use does the database get? Is there a lot of deleting and replacing data? Are a lot of action queries being run? Are there a large number of users doing data entry? In which database are tables being created and deleted? Local tables and action queries will affect the front end but not the back end.

    If you have a lot of people using it and a high volume of transactions, or even a few people but a lot of appending, deleting and make tables, then you should compact and repair frequently. If they use it occasionally to look up information, then you shouldn't have to worry about it unless you used memo fields in your tables. They are prone to corruption, and I generally avoid them.

    You need to include the capability in your application, but the frequency and the method of invoking it depends on the situation.

    JetComp is something else entirely. It allows you to compact without launching Access, which makes it very useful in some situations, especially when you are not able to use the built in compact and repair successfully. But since JetComp is a separate program, you have to either give the user instructions on how to use it or write a script to invoke it if you want to depend on it for your compact and repair.
    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
  •