Welcome to SPN

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

Sign Up Now!
  1. Monthly (Recurring) Target: $300 :: Achieved: $95
      Become a Supporter    ::   Make a Contribution   

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
     
Since you're here... we have a small favor to ask...

More people are visiting & reading SPN than ever but far fewer are paying to sustain it. Advertising revenues across the online media have fallen fast. So you can see why we need to ask for your help. Donating to SPN's is vote for free speech, for diversity of opinions, for the right of the people to stand up to religious bigotry. Without any affiliation to any organization, this constant struggle takes a lot of hard work to sustain as we entirely depend on the contributions of our esteemed writers/readers. We do it because we believe our perspective matters – because it might well be your perspective, too... Fund our efforts and together we can keep the world informed about the real Sikh Sikhi Sikhism. If everyone who writes or reads our content, who likes it, helps us to pay for it, our future would be much more secure. Every Contribution Matters, Contribute Generously!

    Become a Supporter      ::     Make a Contribution     



Share This Page