locked
Older Database crashes when opened in Windows 7 Access 2003 RRS feed

  • Question

  • We have an older Access 2000 database and we are trying to open in windows 7, Access 2003. We know the database is fine and opens fine in Access 2000 on an XP machine.  All of the VBA code was created by Microsoft's wizard.

    We can open the database fine....however, as soon as we look at a table that has a relationship with another table, (bill-template with 1-to-many relationship with bill-template-details, Access crashes.

    We've tried compact and repair and even upgraded the database to 2003 and it makes no difference.  This is the error in the event log.  We also tried the /decompile and creating a .mde but that didn't help either.  I've also tried deleting the relationship for this table. 

    I more thing, the strange thing is I can open the table and see all the data once but as soon as I close the table it crashes and from that point on the table is trashed and I can only see the first entry and Access immediately crashes.

    Faulting application name: MSACCESS.EXE, version: 11.0.8166.0, time stamp: 0x46437912

    Faulting module name: ntdll.dll, version: 6.1.7601.18869, time stamp: 0x55636303

    Exception code: 0xc0000005

    Fault offset: 0x0005615d

    Faulting process id: 0xaf0

    Faulting application start time: 0x01d0cbb712c79f50

    Faulting application path: C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE

    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

    Report Id: 5c009120-37aa-11e5-b0e3-00c0a888038d

    and additional this information:

    Fault bucket , type 0

    Event Name: APPCRASH

    Response: Not available

    Cab Id: 0

    Problem signature:

    P1: MSACCESS.EXE

    P2: 11.0.8166.0

    P3: 46437912

    P4: ntdll.dll

    P5: 6.1.7601.18869

    P6: 55636303

    P7: c0000005

    P8: 00056258

    P9:

    P10:

    Attached files:

    C:\Users\theuser\AppData\Local\Temp\10605800.cvr

    C:\orders\Customer_orders.mdb

    C:\Users\theuser\AppData\Local\Temp\WERD7C3.tmp.WERInternalMetadata.xml

    These files may be available here:

    C:\Users\theuser\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_MSACCESS.EXE_ef610a3fe98e4ef92cac9543191e31d918ce471_0e09e895

    Analysis symbol:

    Rechecking for solution: 0

    Report Id: 37f5f010-37a7-11e5-b0e3-00c0a888038d

    Report Status: 65


    Thank you in Advance.



    • Edited by codeaholic Friday, July 31, 2015 6:05 PM
    Friday, July 31, 2015 5:52 PM

Answers

  • The database wasn't corrupt.  What was corrupt is Microsoft access.  There are two security fixes that never get picked up by Windows update and came after the service pack.  These are more important than the actual service pack. Once those were installed, everything worked great.

    Thank you in Advance.

    • Marked as answer by codeaholic Monday, August 3, 2015 2:59 PM
    Monday, August 3, 2015 2:59 PM

All replies

  • Hi Codeaholic,

    Try to create a new Blank database and import your Tables into it. If this works then import the other items.

    If not look through your tables for corrupt data!

    Good Luck


    Brian, ProcessIT- Hawke`s Bay, New Zealand

    Sunday, August 2, 2015 10:56 PM
  • The database wasn't corrupt.  What was corrupt is Microsoft access.  There are two security fixes that never get picked up by Windows update and came after the service pack.  These are more important than the actual service pack. Once those were installed, everything worked great.

    Thank you in Advance.

    • Marked as answer by codeaholic Monday, August 3, 2015 2:59 PM
    Monday, August 3, 2015 2:59 PM