Can no longer run code

[Rob007]

I am not a new user but I am having a problem that has me stumped!

I have a large database that I have been trying to fix for the last 2 weeks and tried everything I can think of. Problem is that code wont run (I know there are a lot of things to try and fix this).

Today I decided to start at the beginning (would have been nice to think of that earlier) and create a new simple database with only a single form with a single command button running some simple code:
MsgBox "Code has been run", vbOKOnly, "Test"

I get the following error:
Error: "Object or class does not support the set of events"

My conclusion is that my computer is no longer capable of running MS Access. I would love to know why. Let me know if you have any ideas. If not it looks like I will have to uninstall and reinstall.
OS: Vista
Access: 2003

Thanks,
Rob

 

[bohemian9485]

Have you checked your references in VBE? Maybe there are some missing references that's why Access is acting this way...

 

[Rob007]

Thanks Bohemian,

That was one of my guesses as well. I was using some non-standard references. I have tried removing all references except Visual Basic For Applications and Microsoft Access 11.0 Object Library and using code (refer initial post) that doesnt require any extra references. Unfortunately that hasnt helped. Perhaps one of the files that these two references are pointing to has become corrupt?

In the meantime I have tried uninstalling access and reinstalling, including sp3 and fix but this hasnt helped.

 

[bohemian9485]

I think you need the Microsoft Access 11.0 (this is for Access 2K3) Object Library as well

 

[Rob007]

That was the second reference that I mentioned: "I have tried removing all references except Visual Basic For Applications and Microsoft Access 11.0 Object Library..."

Thanks,

Rob

 

[gemma-the-husky]

try access uninstall/reinstall

the main problem here is that a uninstall doesnt fully uninstall, whatever it says, in which case the reinstall doesnt fully reinstall either

you can FORCE a genuine full reinstall of all the dll's etc, with command line switches, but you would need to look at MS knowledge base to get these right, as I am not sure what they are offhand - its just the principle that a normal reinstall wont necessarily do what it says on the tin