On Click error in Acess 2007

[KLP34]

I opened a database that was created in Access 2003 and received the error
message shown below. BTW, everything works fine in A2003. The item I
clicked on was on the first screen. Any information would be appreciated.

"The expression On Click you entered as the event property setting produced
the following error: Object or class does not support the set of events."

 

[vbasean]

Buttons (like other controls) have events. The major event of a button could
be concidered the "On_Click" event

open the form in design view

right click on the button in question and select 'Properties'

Select the 'Events' tab

if you scroll down the list you will see the 'On Click' event

it could be marked with:
- the name of a macro
there's something wrong with the macro, check it out by going to the
'Macros' (listed in the view off to the left of the main window)
- a function
there's something wrong with the function, click [ctl] + [f2] while in
the box.
- or [Event Procedure]
there's something wrong with the VBA procedure. Click on the elipse
button [...] which will guide you VBA window.
- or it's blank.
something got lost in the transition 2003 to 2007

 

[Linq Adams via AccessMonster.com]

When apps run fine on one machine and not on another or run fine in one
version and not under a newer version, the first thing you have to think
about are missing references.

Here are Doug Steele's instructions on how to troubleshoot the problem:

*** Quote ***

Any time functions that previously worked suddenly don't, the first thing to
suspect is a references problem.

This can be caused by differences in either the location or file version of
certain files between the machine where the application was developed, and
where it's being run (or the file missing completely from the target machine).
Such differences are common when new software is installed.

On the machine(s) where it's not working, open any code module (or open the
Debug Window, using Ctrl-G, provided you haven't selected the "keep debug
window on top" option). Select Tools | References from the menu bar. Examine
all of the selected references.

If any of the selected references have "MISSING:" in front of them, unselect
them, and back out of the dialog. If you really need the reference(s) you
just unselected (you can tell by doing a Compile All Modules), go back in and
reselect them.

If none have "MISSING:", select an additional reference at random, back out
of the dialog, then go back in and unselect the reference you just added. If
that doesn't solve the problem, try to unselect as many of the selected
references as you can (Access may not let you unselect them all), back out of
the dialog, then go back in and reselect the references you just unselected.
(NOTE: write down what the references are before you delete them, because
they'll be in a different order when you go back in)

For far more than you could ever want to know about this problem, check out

http://www.accessmvp.com/djsteele/AccessReferenceErrors.html

Just so you know: the problem will occur even if the library that contains
the specific function that's failing doesn't have a problem.

**** End Quote ****