MSAccess 2007 will not run on Win10 computer, using project files.

Question

Hi,

Our client knows MSAccess 2007 is at end of life.

We have a client who can't afford the cost to recode their project file based system to MDB/linked tables.  On some Win10 computers Access 2007 runs fine, on others they get the below event errors after opening the project file.  Any work around other than Win7?

.

Faulting application name: MSACCESS.EXE, version: 12.0.4518.1014, time stamp: 0x4542815c

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0x07b81e40

Faulting process id: 0x34bc

Faulting application start time: 0x01d42840b21bec69

Faulting application path: C:\Program Files (x86)\Microsoft Office\Office12\MSACCESS.EXE

Faulting module path: unknown

Report Id: a5c5f1a2-5051-4a3d-9729-55fc114f88f2

Faulting package full name: 

Faulting package-relative application ID: 

Fault bucket 2249548651528146358, type 5

Event Name: BEX

Response: Not available

Cab Id: 1892379083777237932

Problem signature:

P1: MSACCESS.EXE

P2: 12.0.4518.1014

P3: 4542815c

P4: unknown

P5: 0.0.0.0

P6: 00000000

P7: 07b81e40

P8: c0000005

P9: 00000008

P10: 

Attached files:

\?\C:\Users\THOMAS~1.PHI\AppData\Local\Temp\248551000.cvr

\?\C:\Users\THOMAS~1.PHI\AppData\Local\Temp\248551078.od

\?\C:\Users\thomas.philbrick\Desktop\PROD Admin.adp

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9C62.tmp.WERInternalMetadata.xml

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9C73.tmp.xml

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9C91.tmp.csv

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9D1F.tmp.txt

\?\C:\Users\thomas.philbrick\AppData\Local\Temp\WERAF6F.tmp.appcompat.txt

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAFBF.tmp.mdmp

\?\C:\Users\thomas.philbrick\AppData\Local\Temp\WERB0C9.tmp.WERDataCollectionStatus.txt

These files may be available here:

C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_MSACCESS.EXE_4afea58bb0272c83a61cba9ec0fcb6113221a4c_00000000_cab_3d24b6a1

Analysis symbol: 

Rechecking for solution: 0

Report Id: a5c5f1a2-5051-4a3d-9729-55fc114f88f2

Report Status: 268435464

Hashed bucket: fb3cd05b0419fa922f380094774b4db6

Cab Guid: 80bc8d67-8a2f-4c4f-9a43-14c01cebe3ac

Answer 1

Hello Scott,

The 1st screen below are the references from the new computer before I did anything.  I then checked the modules missing on the new computer to match the 2nd screen shot from the Win10 machine where Access2007 works.  I did have to copy over the MSCAL.OCX for the calendar control.Thanks,

-Tom

Answer 2

Hi Scott,

I made the references the same on the new Win10 machine and still get the same error in event log.  I've asked if the help desk person can build a new computer with the same hardware as the Win10 machine where the apps. work under Access 2007.  Anything else we can try?  

Thanks,

-Tom

Answer 3

Hello Scott,

Thank you for your reply - the machines are 64bit and the most recent ones that don't work are on Win10 1803.  Next chance I get I'll get the references and see if the files exist on the new machine.

Thank you,

Tom

Answer 4

If the application runs fine on some machine but not others, then the trouble is with those environments, not Office.

Are you sure everything is up to date on the machines regarding Windows? That's the most common reason for troubles like this.

Also, are you sure the Access app has all the necessary references? References can be available on MachineA, but not on MachineB, and this can result in troubles like you report. If you can show us a list of the references required by the Access app we could perhaps pinpoint some that might give troubles.

Are all the machines the same "bit-ness" (i.e. 32-bit or 64-bit)?