Command Button Problem

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi All

I have been developing an Access database, using tables and the form wizard. I have inserted a number of command butttons, such as save record, new record, undo record and a few to go to other forms. Everything was working perfectly OK, but all of a sudden I am getting "Ambiguos name detected Find- Customer - Click. Some of the buttons are to find a customer (record) but they all are getting the same error message. I have checked the properties and all buttons appear to be OK and are referencing where I want them to go. I have tried deleting the buttons in a copy database and introducing new ones, but I get the same error. I have also tried running the dtabase on another machine, but I get the same message. An earlier version of the same databse is working OK

The problem is driving me mad, and I don't want the have to redo all my work! Can someone help me please

Regards

Rob
 
This could be because you have two procedures with the same
name. To check this out, open the VB Editor, select from
the ProjectExplorer the form that is giving the error
message and scan down the code to see if you have two lines
that read
Private Sub Find-Customer_Click
If you have, then delete one of the subroutines.

Hope This Helps
Gerald Stanley MCSD
-----Original Message-----
Hi All,

I have been developing an Access database, using tables
and the form wizard. I have inserted a number of command
butttons, such as save record, new record, undo record and
a few to go to other forms. Everything was working
perfectly OK, but all of a sudden I am getting "Ambiguos
name detected Find- Customer - Click. Some of the buttons
are to find a customer (record) but they all are getting
the same error message. I have checked the properties and
all buttons appear to be OK and are referencing where I
want them to go. I have tried deleting the buttons in a
copy database and introducing new ones, but I get the same
error. I have also tried running the dtabase on another
machine, but I get the same message. An earlier version of
the same databse is working OK.
The problem is driving me mad, and I don't want the have
to redo all my work! Can someone help me please?
 
Back
Top