ACCESS and WINMM.DLL problem (still a problem)

I have MSOffice professional on 5 PCs, 4 work fine, on one PC, when I try to run ACCESS to fails with a message informing me of a page fault in respect of WINMM.DLL All 5 PCs are running Win95, all (in theory) set up the same, with software on network server (NT4.0). Any ideas as to cause (and preferably solution......I have reinstalled MS Office several times on offending PC)

I have previously asked this question and had a sensible suggestion for a cure (basically to disable the sound card........but the PC concerned does not have a sound card.) At that point I put the problem on the back-burner since I had more pressing problems. I now need a solution.
               Regards,
               Garry Homer
grhAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

itamarCommented:
Please, find the WINMM.DLL in your Windows/System folder.
Right click it and use option "Quick view" ( i guess that's the English option), compare with the other PC's. If, it's not the same version or it's corrupted copy this file from one of the good PC's.
Check if the Multimidia option is complete unchecked in the Control Panel | Add/Remove software | Windows Installation.
Perhaps there was a multimidia kit installed some day...

IHTH
0
FrankNCommented:
You probably have either a corrupted file, or a bad Registry entry.  You didn't say whether you had an earlier version of Office on the offending PC, but often a re-install isn't sufficient to fix corrupted files or Registry entries.  You must completely *remove* the software in question (in this case, Office), and then reinstall it.  If you just re-install, the installation may see the files that are already there, and not update the new files.

If it's not a corrupted file problem, then your second choice is possibly a bad Registry entry, and you'll need to re-register the DLL in question.  You can use RegSrv32 to do this.  You'll find articles on the Microsoft Tech Support site pertaining to corrupted DLLs and how to re-register them.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Office

From novice to tech pro — start learning today.