By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,986 Members | 2,030 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,986 IT Pros & Developers. It's quick & easy.

Form Conversion 97 to 03

P: n/a
Hello everyone.

I'm converting from 97 to 03, and I'm having trouble with the forms.
Although I can see individual forms on their own, I cannot use command
buttons to jump from one form to the other. When I click on the
command button to open another form, I receive the debugger window in
the background with the error message, "Compile error: Ambiguous name
detected: Relo_Update_Click". In addition, the line "Private Sub
Relo_Update_Click()" is highlighted in blue.

Granted, I may have had a form or macro entitled "Relo Update" at one
time, but I no longer do. In fact, I've tried copying my old form
fields into a new form (minus the command buttons) and creating a new
button for a completely new form. Unfortunately I receive the exact
same error, and at this point I'm not sure what to do.

For those of you who can help me with this, please know that although
I'm comfortable with Access, I do not understand VB very well and thus
am not very good at writing it either. All I want to do is get my
command buttons back so that others who use my forms can continue to do
so without disruption once I convert. Until then, I'm stuck using '97.

Your help would be much appreciated.

Sincerely,

OMan :)

Oct 27 '06 #1
Share this Question
Share on Google+
1 Reply


P: n/a
OMan wrote:
I receive the debugger window in
the background with the error message, "Compile error: Ambiguous name
detected: Relo_Update_Click".
Somehow an extra Relo_Update_Click event was created in one of the forms.
Search for all occurrences of this name and decide which procedure you want
to keep and then delete any other procedures of that name in that form. It's
ok to have the same named procedure in multiple forms if they're all private
though, so be careful that you don't accidentally delete the
Relo_Update_Click procedure in any other forms that only have it once.

--
Message posted via http://www.accessmonster.com

Oct 27 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.