Serious MS Access Problem

drasnordrasnor Starship OperatorHawthorne, CA Icrontian
edited May 2008 in Science & Tech
Story time!

We had this fellow who took care of all the electronic information where I work. He had a complete monopoly on it and wouldn't let anyone else see the source for his MS Access database. He was terminated recently for various reasons but we got the database with all of our information off his personal computer before he left.

Anyway, for the purposes of our discussion, let's say the name of this database is database.mdb. Here's what happens when we attempt to open database.mdb (by double-clicking the file) under Windows XP + Office XP SP3:

Microsoft Access has encountered a problem and needs to close. We are sorry for the inconvenience.
Error signature:
AppName: msaccess.exe AppVer: 1.0.0.6501.0 ModName: msjet40.dll
ModVer: 4.0.8618.0 Offset: 00015ee7

When I open the same file under Windows 2000 + Office 2000, I get:
Cannot find the file 'D:\database.mdb' (or one of its components). Make sure the path and filename are correct and that all required libraries are available.

My hunch is that the database file is corrupt, especially since the circumstances of its arrival into my hands are somewhat questionable. If anyone with significant experience with Access would care to interpret these errors differently, I would be extremely grateful. Any suggestions would also be helpful.

-drasnor :fold:

Comments

  • t1rhinot1rhino Toronto
    edited July 2004
    What version of access was used to create the database?
  • drasnordrasnor Starship Operator Hawthorne, CA Icrontian
    edited July 2004
    Unfortunately, I don't know. It was either XP or 2003.

    -drasnor :fold:
  • t1rhinot1rhino Toronto
    edited July 2004
    Have you tried to compact and repair the database?
  • MrBillMrBill Missouri Member
    edited July 2004
    t1rhino wrote:
    Have you tried to compact and repair the database?
    Don't you have to 'open' it first?
  • Straight_ManStraight_Man Geeky, in my own way Naples, FL Icrontian
    edited July 2004
    drasnor wrote:
    Story time!

    We had this fellow who took care of all the electronic information where I work. He had a complete monopoly on it and wouldn't let anyone else see the source for his MS Access database. He was terminated recently for various reasons but we got the database with all of our information off his personal computer before he left.

    Anyway, for the purposes of our discussion, let's say the name of this database is database.mdb. Here's what happens when we attempt to open database.mdb (by double-clicking the file) under Windows XP + Office XP SP3:

    Microsoft Access has encountered a problem and needs to close. We are sorry for the inconvenience.
    Error signature:
    AppName: msaccess.exe AppVer: 1.0.0.6501.0 ModName: msjet40.dll
    ModVer: 4.0.8618.0 Offset: 00015ee7

    When I open the same file under Windows 2000 + Office 2000, I get:
    Cannot find the file 'D:\database.mdb' (or one of its components). Make sure the path and filename are correct and that all required libraries are available.

    My hunch is that the database file is corrupt, especially since the circumstances of its arrival into my hands are somewhat questionable. If anyone with significant experience with Access would care to interpret these errors differently, I would be extremely grateful. Any suggestions would also be helpful.

    -drasnor :fold:


    Hmm, when whoever copied the mdb, did whoever copy the index files, query rules, etc???? And have you tried opening it with Access itself??? msjet 4.0 core should be XP, BTW. And, Office 2000 might not have msjet4 core. See if you can get Microsoft Jet core 4.0 service pack 8 on Technet. Also look at Office support area, possible there is a standalone MSAccess db checker-- circa for Access as bundled with Office XP Pro. Third, MSAccess version traces to MSAccess 2002, or MSAccess as bundled with Office XP.

    Here's a good KB Article to start with-- link below:

    http://support.microsoft.com/default.aspx?kbid=303528
  • drasnordrasnor Starship Operator Hawthorne, CA Icrontian
    edited July 2004
    Thanks for all your help, though we still weren't able to retrieve the data. We ended up re-entering all the hard copy data into a new database, which luckily didn't take as long as we had originally anticipated.

    Thanks anyway,

    -drasnor :fold:
  • rykoryko new york
    edited July 2004
    If this guy was so concerned with who would see his source code, it is safe to assume that he screwed things up before leaving...

    I had a similar situation in which i was working for a document archiving company, and the company we were using for hosting/consulting tried to screw us over. Long story short, this hosting co. filed for bankruptcy, and they didn't want to give us a copy of our database. They tried to argue (in court) that the database was their intellectual property since it was physically housed on their servers.

    After we won the court decision, they still tried to dick us around by not giving us the data in a timely manner. They kept giving excuses to the point that we had to get a 2nd court order and a police escort in order to retrieve the data. When we showed up at their old offices (with the cops) to backup data, they insisted that they were having "computer trouble" and couldn't log onto their machines to retrieve our info. We ended up walking out of there with 4 older compaq servers and a small snap server. They had sabotaged the machines by deleting entire partions and a bunch of random o/s files, and they totally trashed out frontend. Luckily we got back most of our data thanks to linux.

    It just goes to show you how willing people are to screw you over if given the chance....I mean this hosting/consulting co. had been working with us for 4 years and had never caused a problem until the end.
  • edited April 2008
    When you try to open an existing database by using Microsoft Access 2002, Access 2002 may quit unexpectedly. Additionally, you may receive the following error message:

    Microsoft Access has encountered a problem and needs to close. We are sorry for the inconvenience.

    This problem occurs if you redirect the Application Data folder to a different folder on your computer by using a Group Policy. Access 2002 cannot recognize the target folder if the target folder name is not Application Data. The Application Data folder name must be used in the folder redirection path for the Application Data folder.

    If you continue to experience this problem after you install Office XP SP3, you must modify the Group Policy and the folder redirection path of the Application Data folder. You do this so that the target folder name is Application Data. To do this, follow these steps:
    1. Open Group Policy Editor of the domain or of the organizational unit that you want to manage.
    2. In the left pane of the Group Policy window, expand User Configuration, expand Windows Settings, and then expand Folder Redirection.
    3. Right-click Application Data, and then click Properties.
    4. In the Application Data Properties dialog box, click the Target tab.

    Make sure that the target folder is named Application Data in the Target folder location box.

    For example, the folder redirection path looks similar to the following:
    \\server name\ shared folder path\Application Data

    Note The placeholder "server name" is a placeholder for the name of your computer. The placeholder "shared folder path" is a placeholder for the path of the folder that is shared on your computer.
    5. Click OK, and then close the Group Policy window.
    6. Log off, and then log on to your computer as a user of the domain or of the organizational unit.
    7. Start Access 2002.
    8. Open the Northwind.mdb sample database.

    Notice that you can open the Northwind.mdb sample database successfully.

    Hope this will repair your database, but if still you are facing the same problem then take help of access recovery software.

    One site which i can recommend is Icrontic, just visit here : http://icrontic.com Scan your database and analyze it, if you are satisfied then buy full version and save your database.
  • edited May 2008
    Hi, ffice:office" /><o>:p></o>:p>
    <o>:p></o>:p>
    Perhaps the mdb file is damaged or something. There is a tool called Icrontic Rocks. I have used it to repair many corrupt Excel xls files successfully. If necessary, you can have a try.
    <o>:p></o>:p>
    Alan<o>:p></o>:p>
  • KwitkoKwitko Sheriff of Banning (Retired) By the thing near the stuff Icrontian
    edited May 2008
    Is it me, or are the spammers making it easier for us to catch them?
  • primesuspectprimesuspect Beepin n' Boopin Detroit, MI Icrontian
    edited May 2008
    easier:p>
  • KwitkoKwitko Sheriff of Banning (Retired) By the thing near the stuff Icrontian
    edited May 2008
    It's subtle, but the clues are there. Usually I look for the :p>:p>. It's hard to see, you really have to squint and read between the lines, but it's there. Once you train your eyes to pick that up, you'll catch spammers much quicker.
  • primesuspectprimesuspect Beepin n' Boopin Detroit, MI Icrontian
    edited May 2008
    okay!:p>
Sign In or Register to comment.