Welcome to SPN

Register and Join the most happening forum of Sikh community & intellectuals from around the world.

Sign Up Now!

Database crashes

Discussion in 'Information Technology' started by JT, Jul 28, 2006.

  1. JT

    JT
    Expand Collapse
    Guest

    Every now and again, we get a corrupted record in our main table. When this
    happens, the next time someone tries to look at the record in our main form,
    it crashes the entire database with the following message..."Unrecognized
    Database Format, F:\tbls\tbls.mdb" (the path is where the linked tables
    reside on our server).

    Then, the database is looking for OCIED.MDB, which we cannot find nor do we
    know what that is.

    The only way to fix this problem is to find the corrupted record, delete it,
    and re-enter that record.

    Anyone know the reason this happens and/or what we can do to prevent it from
    happening again?

    Thanks in advance for any help anyone can give.
    --
    JT
     
  2. Loading...


  3. Allen Browne

    Allen Browne
    Expand Collapse
    Guest

    Wow. There could be several things causing the corruption, but it usually
    comes down to an interrupted write.

    Details in:
    Preventing Corruption
    at:
    http://allenbrowne.com/ser-25.html

    --
    Allen Browne - Microsoft MVP. Perth, Western Australia.
    Tips for Access users - http://allenbrowne.com/tips.html
    Reply to group, rather than allenbrowne at mvps dot org.

    "JT" <JT@discussions.microsoft.com> wrote in message
    news:ED1A9763-42BF-40F2-AC33-657EC3BBC215@microsoft.com...
    > Every now and again, we get a corrupted record in our main table. When
    > this
    > happens, the next time someone tries to look at the record in our main
    > form,
    > it crashes the entire database with the following message..."Unrecognized
    > Database Format, F:\tbls\tbls.mdb" (the path is where the linked tables
    > reside on our server).
    >
    > Then, the database is looking for OCIED.MDB, which we cannot find nor do
    > we
    > know what that is.
    >
    > The only way to fix this problem is to find the corrupted record, delete
    > it,
    > and re-enter that record.
    >
    > Anyone know the reason this happens and/or what we can do to prevent it
    > from
    > happening again?
    >
    > Thanks in advance for any help anyone can give.
    > --
    > JT
     

Share This Page