Results 1 to 5 of 5
  1. #1
    3 Star Lounger
    Join Date
    Jul 2001
    Location
    Minneapolis, Minnesota, USA
    Posts
    299
    Thanks
    0
    Thanked 0 Times in 0 Posts

    compacting problems (A97) (Access 97)

    We have a .db that doesn't want to compact. The compact starts fine, db1.mdb is created and right before the process replaces db1.mdb as the updated application, we get:

    Record(s) can't be read, no read permission on (path)(name).mdb

    No one is in the database when it compacts. We've tried moving the db to another server, and even to a standalone hard drive but still get the error, just a different path.

    We previously had to rebuild this database last month, and everything was going fine until last Friday. <img src=/S/hairout.gif border=0 alt=hairout width=31 height=23>

    Any suggestions?
    Carpy Diem, it&#39;s .

  2. #2
    3 Star Lounger
    Join Date
    Jan 2001
    Location
    Edmonton, Alberta, Canada
    Posts
    326
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: compacting problems (A97) (Access 97)

    I also get that occasionally.

    I've found that when I get that error using Jetcomp I normally end up with a functional database that doesn't appear to have lost anything of significance (I don't know whether the same would apply when using the compact menu item in Access - if I have any problems within Access I always try Jetcomp). What you may lose in the repaired database is your startup options - just reset them if that happens.

    Note that I always use split databases (with a separate frontend and backend) so I'm not worried about losing "real" data. Almost invariably, if anything "goes south" it's one of my frontends.

  3. #3
    4 Star Lounger
    Join Date
    Feb 2001
    Location
    Gillingham, Kent, England
    Posts
    511
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: compacting problems (A97) (Access 97)

    If compacting and repairing both fail and you don't have any luck with Jetcomp, you might like to try making a new database and importing everything from your old one (I have found this has worked before when all else has failed). To do this, in the new database select get external dataimport, and then just select everything.

  4. #4
    3 Star Lounger
    Join Date
    Jul 2001
    Location
    Minneapolis, Minnesota, USA
    Posts
    299
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: compacting problems (A97) (Access 97)

    The JetComp gave the same irritating error message so right now I'm rebuilding the database. <img src=/S/compute.gif border=0 alt=compute width=40 height=20>
    Hopefully, we can keep an eye on this so we can figure out why it's <img src=/S/meltdown.gif border=0 alt=meltdown width=15 height=15> every two weeks or so...

    Thanks for everyone's help!!!
    Carpy Diem, it&#39;s .

  5. #5
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,624
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: compacting problems (A97) (Access 97)

    Some things that you might want to look at as the source of your corruption:

    1 - Use of memo fields in the table design makes it significantly more fragile - avoid them if you can, or use an alternative table source such as SQL Server.
    2 - Corruption most frequently occurs in the queries, forms, reports and code part of your database, so consider splitting it into a front-end and a back-end, and make the front-end an MDE.
    3 - A further trick is to make the front-end database read-only (as long as you don't have any local tables that need modification, such as the switchboard items table). Access always seems to think it should write to a database when it opens it, and this prevents that from happening.
    4 - Take a hard look at all the workstations running the database and see if any of them are flakey - crashes while doing things in Access often cause database corruption.
    5 - If you can split the front-end database away, consider putting it on each workstation, which gives better performance, and also isolates who the culprit is if you have a flakey workstation.

    Hope this helps.
    Wendell

Posting Permissions

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