Welcome to SPN

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

Sign Up Now!

msjet40 - Urgent Help Needed

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

  1. Curious1975

    Curious1975
    Expand Collapse
    Guest

    My database has been crashing on a regular basis for the past several months
    with two major crashes and repairs by our main IT guy. Today I am receiving
    the usual

    "...is not a database...do you want to repair error..." which we usually get
    and then it will repair itself. The last time, however, it will not repair
    itself. It's giving me one of those "do you want to send this error to
    Microsoft" messages. I am not getting any error information other than when
    I click on the "do you want to send this message to Microsoft" it tells me
    the problem lies within the msjet40.

    Can anyone guide me in the process of figuring out what to do? Please.
     
  2. Loading...

    Similar Threads Forum Date
    URGENT PLZZ HELP: KAAM LUST BODY MASSAGE SPA ISSUE Sikh Youth Jul 9, 2015
    Sikh News Spate Of Attacks By Islamist Insurgents Rattle Sikh Community In Pakistan Breaking News Apr 19, 2015
    SciTech Urgent Need to Remove Space Debris Breaking News Apr 25, 2013
    Urgent! Need help with some gender equality questions! Questions and Answers Jan 7, 2013
    General URGENT! Video on reality of sexual grooming gangs in the UK - please share Hard Talk Nov 21, 2012

  3. John Vinson

    John Vinson
    Expand Collapse
    Guest

    On Wed, 14 Jun 2006 13:16:02 -0700, Curious1975
    <Curious1975@discussions.microsoft.com> wrote:

    >My database has been crashing on a regular basis for the past several months
    >with two major crashes and repairs by our main IT guy. Today I am receiving
    >the usual
    >
    >"...is not a database...do you want to repair error..." which we usually get
    >and then it will repair itself. The last time, however, it will not repair
    >itself. It's giving me one of those "do you want to send this error to
    >Microsoft" messages. I am not getting any error information other than when
    >I click on the "do you want to send this message to Microsoft" it tells me
    >the problem lies within the msjet40.
    >
    >Can anyone guide me in the process of figuring out what to do? Please.


    Good luck. I hope you have the database backed up!

    Check out the resources and links at

    http://www.granite.ab.ca/access/corruptmdbs.htm

    John W. Vinson[MVP]
     
  4. Curious1975

    Curious1975
    Expand Collapse
    Guest

    Thanks for the link.

    I forgot to mention that I am completely unable to open the database. It
    will not repair or open and it it not really giving me any error messages,
    which I find strange.

    Unfortunatey, I am not a database administrator so I am not too well versed
    in how to repair these types of things. I was hoping someone could tell me
    if it was a so-called fatal error or if there was hope in someway salvaging
    it.

    Thanks.



    "Curious1975" wrote:

    > My database has been crashing on a regular basis for the past several months
    > with two major crashes and repairs by our main IT guy. Today I am receiving
    > the usual
    >
    > "...is not a database...do you want to repair error..." which we usually get
    > and then it will repair itself. The last time, however, it will not repair
    > itself. It's giving me one of those "do you want to send this error to
    > Microsoft" messages. I am not getting any error information other than when
    > I click on the "do you want to send this message to Microsoft" it tells me
    > the problem lies within the msjet40.
    >
    > Can anyone guide me in the process of figuring out what to do? Please.
     
  5. John Vinson

    John Vinson
    Expand Collapse
    Guest

    On Wed, 14 Jun 2006 14:06:01 -0700, Curious1975
    <Curious1975@discussions.microsoft.com> wrote:

    >Unfortunatey, I am not a database administrator so I am not too well versed
    >in how to repair these types of things. I was hoping someone could tell me
    >if it was a so-called fatal error or if there was hope in someway salvaging
    >it.


    Very few Access applications have "database administrators" - I'm not
    one either, though I administer a lot of Access databases.

    All I can suggest is that you carefully read Tony's webpage and follow
    the instructions.

    It's quite possible that this database is irretrievably toasted; it's
    also possible that it can be salvaged. Without following the steps for
    recovering a damaged database there's no easy way to tell.

    John W. Vinson[MVP]
     
  6. Curious1975

    Curious1975
    Expand Collapse
    Guest

    Turned out that it was not repairable. Ended up restoring from the previous
    night and losing an entire days worth of work. Thanks for the assistance and
    sorry for the late reply back.

    "John Vinson" wrote:

    > On Wed, 14 Jun 2006 14:06:01 -0700, Curious1975
    > <Curious1975@discussions.microsoft.com> wrote:
    >
    > >Unfortunatey, I am not a database administrator so I am not too well versed
    > >in how to repair these types of things. I was hoping someone could tell me
    > >if it was a so-called fatal error or if there was hope in someway salvaging
    > >it.

    >
    > Very few Access applications have "database administrators" - I'm not
    > one either, though I administer a lot of Access databases.
    >
    > All I can suggest is that you carefully read Tony's webpage and follow
    > the instructions.
    >
    > It's quite possible that this database is irretrievably toasted; it's
    > also possible that it can be salvaged. Without following the steps for
    > recovering a damaged database there's no easy way to tell.
    >
    > John W. Vinson[MVP]
    >
     
  7. John Vinson

    John Vinson
    Expand Collapse
    Guest

    On Tue, 27 Jun 2006 06:56:02 -0700, Curious1975
    <Curious1975@discussions.microsoft.com> wrote:

    >Turned out that it was not repairable. Ended up restoring from the previous
    >night and losing an entire days worth of work.


    Just breathe a deep sigh of relief that you HAD a daily backup. There
    are all too many folks whose "current backup" is a month old, and even
    more who say "backup? we need backups!?"

    John W. Vinson[MVP]
     

Share This Page