It would help to see the code and know where it was put.

Ambiguous name usually means you have two routines with the same name within
the same 'scope'.

Also, worksheets can have an event associated with a change in a cell on the
sheet, it would be within the worksheet's code module. It would be named
Private Sub Worksheet_Change(...)
'code to execute when a change occurs on the worksheet
End Sub

Look in your VBA project for the word Change and see where it appears, and
that will probably clue you in on either 2 routines with the same name, or if
VBA is being confused somehow by a routine named Change and the
Worksheet_Change() event processor for that worksheet.


"Derrick" wrote:

i have a set of code/macro called Change for my sheets, which hides
rows/enters formulas for whenever a cell 'b3' is changed to another option
from a validated list.
however, for some reason now, a Microsoft Visual Basic notice box pops up
and says "Ambiguous name detected: Change" when i imput data into any cell.
any ideas as to why?