• MS Access XP Crashing

    • This topic has 3 replies, 2 voices, and was last updated 12 months ago by mohamed.

    We used to be a big user of MS Access, but we are down to about a half dozen databases that some of our users still rely on. About a month ago, I noticed that I could not get my Access to stay up long enough to check out some static IP address. Gradually, many of the users that rely on Access had the same thing happen: The database opens, then crashes and goes away. There are still a few people that this has not  happened to. We have tried compatibility settings, removed various Windows Updates, but Access still refuses to stay open. We tried using Access 2010, and that works fine. We even have a RemoteApp option with Office 2003, and that works. (It is not perfect, but it is our go-to workaround.)

    Has anyone else run into problems with Access XP (2002)? Or perhaps we are the last shop to use this ancient version of Access.

    The event viewer log is not very helpful: Event ID 1000

    Faulting application name: MSACCESS.EXE, version: 10.0.2627.1, time stamp: 0x3aa5f86a
    Faulting module name: unknown, version:, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x0019fd50
    Faulting process id: 0x2d40
    Faulting application start time: 0x01d7938b211eedfa
    Faulting application path: C:\Program Files\Microsoft Office\Office10\MSACCESS.EXE
    Faulting module path: unknown
    Report Id: dbc12fe3-d780-4b8b-aadf-bb5dc29370eb
    Faulting package full name:
    Faulting package-relative application ID:

    Event ID 1001:

    Fault bucket 1154781822642381268, type 5
    Event Name: BEX
    Response: Not available
    Cab Id: 0

    Problem signature:
    P2: 10.0.2627.1
    P3: 3aa5f86a
    P4: unknown
    P6: 00000000
    P7: 0019fd50
    P8: c0000005
    P9: 00000008

    Attached files:

    These files may be available here:

    Analysis symbol:
    Rechecking for solution: 0
    Report Id: dbc12fe3-d780-4b8b-aadf-bb5dc29370eb
    Report Status: 268435456
    Hashed bucket: 7ea1f158d2d735d200069bf30bad61d4
    Cab Guid: 0

    Thanks for any help or insights into this.

    Viewing 2 reply threads
    • #2384406

      Exception code 0xc0000005 idicates a memory access violation and thats very deep error.
      I think your 2002 XP version may be out-of-date too much..

      ++ I would try to run your database in newer version of MS Access.
      ++ Better option is: if your users simply work with datatabase application (and do not change the source code) you can run it through MS Access “Runtime version”. Download 2013 version here. We use 2013 version and it works flawlessly.

      Let us know how things work with runtime access.

      Dell Latitude 3420, Intel Core i7 @ 2.8 GHz, 16GB RAM, W10 22H2 Enterprise

      HAL3000, AMD Athlon 200GE @ 3,4 GHz, 8GB RAM, Fedora 29

      PRUSA i3 MK3S+

      1 user thanked author for this post.
    • #2384429

      Thank you so much for your suggestion. This seems to work on my system. I will try it on one of our other users. Is there a way to password the custom workgroup .mdw to the database? It does not work if I add it after the database name. (I was hoping that would work.) Or is there a switch I need to use.


    • #2485682

      one form only crash every time i open and try to enter new data

    Viewing 2 reply threads
    Reply To: MS Access XP Crashing

    You can use BBCodes to format your content.
    Your account can't use all available BBCodes, they will be stripped before saving.

    Your information: