Avatar of Rob4077
Flag for Australia asked on

MS Access crash but only on one machine

I have developed a few MS Access applications using my laptop and up until recently all worked fine. Over the last few weeks I have been experiencing some 'MS Access has crashed - can I tell Microsoft' type errors when running a few of the queries. It is consistent. The same queries crash the same time every time. I tried spending hours fixing with no success so then I tried copying the entire application to another machine and it works faultlessly. I then tried repairing MS Access on my laptop but it didn't fix the problem. Then I tried removing and re-installing MS Access and still no change. Does anyone have any suggestions as to what I can try next?
The version that is crashing is MS Access 2003. I also have MS Access 2007 on my machine and the application runs fine on 2007, however for the sake of my users I need to stick with 2003.
Microsoft Access

Avatar of undefined
Last Comment

8/22/2022 - Mon

On the second machine, where it works faultlessly, do you also have Access 2007 installed?  If not, I am guessing you have a reference problem on the laptop, i.e. you opened the applicaton in Access 2007 and one or more of the references changed to a later version.  Now when you run the app in Access 2003 it breaks due to the incorrect reference.  Check the references between the app on the second machine and the app on the laptop.

OM Gang

Thanks for the suggestion. I have checked the references on both machines and they are identical.
Scott McDaniel (EE MVE )

Try building a new, blank database (on the machine with 03 installed) and importing everything from the old db to the new. It sounds as if you may have some corruption issues, and if the suggestion by om gang didn't work then this is the next step.

Also, make SURE to work carefully with this. Save a backup off-machine (USB stick or something) before doing ANY major operation, such as this import. If you do have to recover the database, your chances are much, much better with a "clean" copy of the bad database ...
Your help has saved me hundreds of hours of internet surfing.

Thanks for the suggestion.

I started trying your suggestion and I am having some real problems.
1. It keeps crashing when I try to copy some objects over (one query and one module - though it does appear to have copied them over even though Access crashed in the process).  
2. I then tried to open the offending query in the new database but MS Access crashed.
3. I then opened the old version (the one that doesn't work on my 2003) using Access 2007 and opened then tried to view the offending query, no problem.
4. I copied the SQL code from the old query in (viewed in Access 2007) into a new query in the new 2003 database and it copied and ran perfectly.
5. I then deleted the original offending query in my new database and renamed the new query to the name of the query I had deleted (so it completely replaced the old query) and tried to run it but MS Access crashed.

What I don't understand is that I have taken this existing copy that won't work on my machine and copied it to 3 other machines now and it works fine on all of those machines using MS Access 2003 and it also works on my machine if I run it from Access 2007. That makes me believe that the real problem is a corrupt MS Access 2003 on this machine. Yet I have tried a repair as well as a remove and re-install of MS Access (through the changes option in control panel > Add or remove programs) and I have tried running a registry cleaner in between removal and re-install. I didn't really want to completely remove Office (all components) and re-install it but I am wondering if that will be needed.

This is wasting so much time and I am gettting nowhere. Any suggestions???

Ok I have had a look at the event log and here's the error message. What on earth do I do to fix it? MS Access is getting more and more unreliable. Now I can't even open other applications that have worked for years. I tried the link and

Event Type:      Error
Event Source:      Microsoft Office 11
Event Category:      None
Event ID:      1000
Date:            23/07/2008
Time:            6:04:44 PM
User:            N/A
Computer:      ROBSUE
Faulting application msaccess.exe, version 11.0.8166.0, stamp 46437912, faulting module msjtes40.dll, version 4.0.9502.0, stamp 44859905, debug? 0, fault address 0x00012923.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
0000: 00700041 006c0070 00630069 00740061
0010: 006f0069 0020006e 00610046 006c0069
0020: 00720075 00200065 006d0020 00610073
0030: 00630063 00730065 002e0073 00780065
0040: 00200065 00310031 0030002e 0038002e
0050: 00360031 002e0036 00200030 00360034
0060: 00330034 00390037 00320031 00690020
0070: 0020006e 0073006d 0074006a 00730065
0080: 00300034 0064002e 006c006c 00340020
0090: 0030002e 0039002e 00300035 002e0032
00a0: 00200030 00340034 00350038 00390039
00b0: 00350030 00660020 00650044 00750062
00c0: 00200067 00200030 00740061 006f0020
00d0: 00660066 00650073 00200074 00300030
00e0: 00310030 00390032 00330032 000a000d
Scott McDaniel (EE MVE )

This sounds like issues with Jet, not necessarily Access. What operating system are you running? What versions of Access/Office do you have on the machine?
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.

Following is a dump of the System Summary

MS Access 2003 is the one that is crashing. Summary follows:
Application name      Microsoft Access
Version      11.0
Build      8166
Product ID      70145-745-8486504-57506
Application path      C:\Program Files\Microsoft Office\OFFICE11\
Language      English (United States)
ADO version      Not Available
VBA version      6.05
References      Not Available

System Summary follows:
OS Name      Microsoft Windows XP Professional
Version      5.1.2600 Service Pack 3 Build 2600
OS Manufacturer      Microsoft Corporation
System Manufacturer      Sony Corporation
System Model      VGN-SZ28GP_C
System Type      X86-based PC
Processor      x86 Family 6 Model 14 Stepping 8 GenuineIntel ~2000 Mhz
BIOS Version/Date      Phoenix Technologies LTD R0082N0, 29/06/2006
SMBIOS Version      2.31
Windows Directory      C:\WINDOWS
System Directory      C:\WINDOWS\system32
Boot Device      \Device\HarddiskVolume1
Locale      United States
Hardware Abstraction Layer      Version = "5.1.2600.5512 (xpsp.080413-2111)"
Total Physical Memory      1,024.00 MB
Available Physical Memory      301.32 MB
Total Virtual Memory      2.00 GB
Available Virtual Memory      1.96 GB
Page File Space      2.40 GB
Page File      C:\pagefile.sys


Oh and for Jet Core Components the dump is. Sorry but I don't know what you're looking for so I've given you the lot.

Description      Debug
Path      Not Available
Description      Excel
Path      C:\Program Files\Microsoft Office\OFFICE11\msaexp30.dll
Version      11.0.8153
Description      Exchange
Path      C:\WINDOWS\system32\msexch40.dll
Version      4.00.9502.0
Description      Jet 2.x
Path      C:\WINDOWS\system32\msrd2x40.dll
Version      4.00.9502.0
Description      Jet 3.x
Path      C:\WINDOWS\system32\msrd3x40.dll
Version      4.00.9502.0
Description      Jet 4.0
Path      Not Available
Description      Lotus
Path      C:\WINDOWS\system32\msltus40.dll
Version      4.00.9502.0
Description      ODBC
Path      Not Available
Description      Paradox
Path      C:\WINDOWS\system32\Mspbde40.dll
Version      4.00.9502.0
Description      SharePoint
Version      11.00.8161.0
Description      Text
Path      C:\WINDOWS\system32\mstext40.dll
Version      4.00.9502.0
Description      Xbase
Path      C:\WINDOWS\system32\msxbde40.dll
Version      4.00.9502.0


I have to admit that I am very concerned about this one. I just looked back at my question history and confirmed this is a repeat of a problem that I had back in June 2006. I tried every possible solution recommended by experts back then and in the end I planned on contacting Microsoft but instead fixed it by re-loading Windows and all the software. How did I get myself into this predicament? If you have any suggestions that aren't listed on this link please let me know. If you don't have any suggestions let me know and I guess I will start re-building the computer again.
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck
Scott McDaniel (EE MVE )

View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.

Thanks for the suggestion. Is there somewhere on the MS Web site where I can raise an issue? The only way I know to get in touch with Microsoft is to phone them.

Ok I found the MS support system - looks like I will have to phone them.

Meantime can you tell me how to re-install Jet?

Thanks for all your help. I have contacted MS Support and now they're unsure which department should be helping me. In the meantime I am going to double the RAM in this machine and use some other software I have to create a virtual machine in the machine so I can use 2003 on one virtual machine and 2007 on the other virtual machine. That way there should be no conflicts.

Appreciate your patience and support on this one.
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
Scott McDaniel (EE MVE )

<create a virtual machine in the machine so I can use 2003 on one virtual machine and 2007 on the other virtual machine>

That's what I do, and what most professional Access devs do as well. If you must deploy to users with 2003 then I'd STRONGLY suggest you do your development work in the 2003 environment, and do you final compile/build in the 2003 environment. In other words, always work with the "lowest common denominator" when doing this. If you have users running Access 2000, then build your application in Access 2000 ... if you have users running Outlook 10, then make sure that your references point to Outlook 10 ... etc etc

I wish I had known that before I tried loading both versions on the same machine. I have basically wasted 3 full days work this week trying to figure it out the hard way. I guess this is all part of the learning process. Thanks for your continued patience and help, not just with this one but with all the others you've contributed to.