On Click Error

  • Thread starter Thread starter Roger Bell
  • Start date Start date
R

Roger Bell

I have a Data Base that loads to the Main Menu, within which users have
several choices. The Command buttons were working fine until recently, when
the following message started appearing:
"The Expression On Click you entered as the Event Property setting produced
the following error: Return without GoSub *The expression may not result in
the name of a Macro. The name of a user defined function or (Event
Procedure). There may have been an error evaluating the function event or
Macro"
I copied the Data Base to another Computer and the Command buttons all work
as they should. I have done a Compact and Repair and Access Repair on the
Problem Computer to no avail. There are other data Bases that run on this
computer with a similar design and they all work fine.
Could anyone kindly advise what the problem could be?

Many thanks for any help
 
Did you check for bad or missing refrences in the code window? maybe that
comp has a missing service pack.

Richard
 
Thanks for that Richard,

As I am a newbie, how do I check for bad references in the code window?
What i do not understand is that all the other data bases on the problem
computer open without a hitch.

Thanks again
 
References are maintained for each individual database file, so one file
might have problems while the others do not.

Try following these steps (from a post by Douglas Steele, MVP):

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://members.rogers.com/douglas.j.steele/AccessReferenceErrors.html
 
To do its job, Access makes use of various external program and object
libraries. If you move a database from one machine to another, these
references may be "broken".

When this happens, you need to take steps to let Access repair the
reference(s) ON THE COMPUTER WHERE THE FAILURE IS OCCURING.

Here are MVP Doug Steele's instructions for how to do it:

*** Quote ***
....
Open the database in design mode.

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

**** End Quote ****

John Spencer
Access MVP 2002-2005, 2007-2009
The Hilltop Institute
University of Maryland Baltimore County
 
Back
Top