Results 1 to 7 of 7
  1. #1
    5 Star Lounger
    Join Date
    Jul 2001
    Location
    NJ, USA
    Posts
    617
    Thanks
    0
    Thanked 0 Times in 0 Posts

    compacting (Access XP)

    Is there any evidence or possibility that the repair and compact function of Access could delete or damage data/

  2. #2
    Gold Lounger
    Join Date
    Feb 2001
    Location
    Sint Niklaas, Belgium
    Posts
    2,778
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: compacting (Access XP)

    It never happens to me (in 95, 97 and 2000).
    If you are afraid of loosing something, make a copy of the database before compact and repair.
    Francois

  3. #3
    5 Star Lounger
    Join Date
    Jul 2001
    Location
    NJ, USA
    Posts
    617
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: compacting (Access XP)

    We are in a chase your tail situation. Trying to figure out why we lost a bunch of records. This is one of the last possibilities that I needed to explore. I have the user compact weekly to keep it tidy. I am thinking strongly that it is being corrupted by another stand alone program that in the last three weeks after an update has been crashing the system. Thanks Fay

  4. #4
    Gold Lounger
    Join Date
    Feb 2001
    Location
    Sint Niklaas, Belgium
    Posts
    2,778
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: compacting (Access XP)

    I can't say more than in my previous post as I install XP only a week ago and have not use compact and repair in this version.

    If it can be of any use for you, FMS Inc has a utility Total Visual Agent that can make backups of your database even if it is open. You can find a trial version on the same link.

    HTH
    Francois

  5. #5
    New Lounger
    Join Date
    Apr 2002
    Location
    Sydney, NSW, Australia
    Posts
    13
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: compacting (Access XP)

    Fay
    I haven't found that the repair/compact function will damage a database if the database is working normally, BUT if the database is already a little damaged (ie doing strange things) SOMETIMES it makes it even worse. This has happened to me mainly in Access 97 & 2000.

    If the DB is behaving strangely I always copy the database before I try and repair it. That way I can at least try something else if it does make it worse.

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

    Re: compacting (Access XP)

    I have to second Francois here. I've never had a compact corrupt a database in any version of Access ... and I started with version 1.0! Missing records could conceivably happen if you had some minor corruption in the data and then did a compact, but I would be extremely surprised to see it. If there was that much corruption, I would expect the whole database to go up in flames, not just a few records. It is far more likely that missing data had a human cause. <img src=/S/sorry.gif border=0 alt=sorry width=15 height=15>
    Charlotte

  7. #7
    5 Star Lounger
    Join Date
    Jul 2001
    Location
    NJ, USA
    Posts
    617
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: compacting (Access XP)

    I am coming to the conclusion that it has something to do with a state program that is an Access based program. They updated the program about four weeks ago and then with the database that is missing records and state program opened it crashed. It has since crashed multiple times.

    Looking at the missing data there is absolutely no pattern either with a particular patient or staff member for the service tickets that are missing. There are records missing out of two tables. One table is missing most of the date/time stamps for when they were entered. And the ClientID number went went from X-###### to just the six digits. We archived staff members but records are missing for active and non-active staff members. None of this would support the assumption of cascading deletion of records. If she accidentally hit the delete button she would have had to say yes to the message. And I don't think she would for thousands of records. Nor does that explain the ID# changes.

    I think the database has been flamed by the state.

    I would be interested in if you think my line of reasoning is off or on. Thanks!

    Fay

Posting Permissions

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