Results 1 to 5 of 5
  1. #1
    3 Star Lounger
    Join Date
    Sep 2002
    Posts
    294
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Crash & Burn (2000)

    One of our access databases is displaying the message below.

    Anyone know if its recoverable ?., I can't import into a fresh database either.

    This is the message shown on opening. it then blows you out.
    Attached Images Attached Images

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Crash & Burn (2000)

    The message in your post is very generic; it's impossible to draw any conclusions from it other than that a problem has occurred.

    The thread starting at <post#=242485>post 242485</post#> contains some ideas about repairing databases and retrieving data from a corrupt database. If you have a non-corrupt recent backup, it might be easier to go back to that.

  3. #3
    Platinum Lounger
    Join Date
    Dec 2001
    Location
    Melbourne, Australia
    Posts
    4,594
    Thanks
    0
    Thanked 27 Times in 27 Posts

    Re: Crash & Burn (2000)

    Save the database, then try a repair (/repair) as part of the command line startup options. Do this from a shortcut.

    Pat

  4. #4
    3 Star Lounger
    Join Date
    Sep 2002
    Posts
    294
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Crash & Burn (2000)

    Thanks for the suggestions guys.. it appears that the file is knackered.


    Surely someone has designed a database program where all this corruption nonsense doesn't occur ???

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

    Re: Crash & Burn (2000)

    <P ID="edit" class=small>(Edited by charlotte on 23-Apr-03 06:24. for an afterthought)</P>Databases, by their nature, are delicate creatures and subject to problems like this. The first one I worked with in the late 1970s had corruption problems and so has everyone since then. The XP version of Access seems to blow up more in the development stages than the previous versions, but I suspect that I've forgotten all the AE, GPF, etc., errors I encountered when developing in the earlier versions.

    If you can't create a new database and import most or all of the objects from this one, then it is indeed knackered. I must say that I had that happen once, but I was working with Visual Source Safe and was able to pull out an earlier version of the application without any problems and without the errors and reapply the changes I was making. I did it *very* carefully though, because I have a strong suspicion that the catastrophic failures like this are related to code errors that aren't obvious.

    BTW, before you try importing objects into a new database, make sure you kill the ldb files from the one that got toasted, and don't try to open it again after you kill the lock files.
    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
  •