Results 1 to 4 of 4
  1. #1
    Join Date
    Aug 2009
    Posts
    4

    Unanswered: Access crashes opening DBF

    Does anyone have any suggestion for fixing this problem: We are using Access 2000 and linking to DBF tables that are generated overnight. On several computers we are using Access 2003. All are running XP pro. All but two are working fine. On my computer, just all of a sudden, when Access tries to open the dbf, Access crashes with no error message. This happened about 2 weeks ago. I can't think of what could have changed. The only Windows update before that was about 2 weeks before that, so I doubt that messed it up. I uninstalled Access 2003 and installed Access 2000 but it still does it. Tried 'repair', still nothing. Any ideas as to where to look or how to fix it?
    Thanks,
    Cass

  2. #2
    Join Date
    Aug 2009
    Posts
    4
    A second computer has a problem opening the DBF's also. This one has Access 2003 also. Each time you launch Access, it has to reinstall something, then when you try to open a DBF you get the error message:
    "Run Time Error 3170 - Could not find installable ISAM". I wonder if the error on both computers is related?
    Any kind of suggestion would be appreciated.
    Thanks,
    Cass

  3. #3
    Join Date
    Aug 2009
    Posts
    4
    Since nobody replied, I broke down and paid for Microsoft support. Turns out that it was trying to use the Borland Database Engine to open the DBF's. I hadn't looked at the DBF's for sometime now (maybe not since reinstalling the op system) and when I did it gave me an error message that it couldn't open the file. I tried it again and it open fine. Apparently it set something in the registry to fix itself and thus crashed Access after that. The solution was to tell Access not to use the Borland engine by adding the following key:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engi nes\Xbase
    Add the keyword (dword) BDE and set the value to 2.

    The second similar problem was not for the same reason and I didn't want to have to pay seperately for both but he did discuss it with me. It sounds like windows didn't install an Access component so that when Access runs it tries to install it. However, since it's Windows that is supposed to install it, Access never can so it's destined to repeat itself. I haven't fixed it, but at least I know where to look.
    ..Cass

  4. #4
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    Thanks for posting the solution
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •