#Name? Error Mystery

[danno-c]

I am seeing #Name? in all textboxes that populate using a multi column
combobox lookup.

Textbox Code Example =[Driver_combo].[column](n)

Everything was working as it should when I was putting it together and saved
it. The next day when I opened it up, all of the autopopulate textboxes
displayed #Name? error.

Also I had a date field that used the ActiveX Calendar Control (mscal.ocx)
this too was working as it should the day before and now I get an Ambiguous
Name Detected error when I run the control.

I checked for updates and I'm OK there, I did a DB repair, and even though
nothing was changed from the time it was working fine, I double checked all
spelling and ran a clean virus check.

It looks to me like the entire form had some kind of gremlin booger it up
overnight. Any ideas on what could have happened?

Thanks
Dan

 

[Rod Plastow]

I am seeing #Name? in all textboxes that populate using a multi column
combobox lookup.

Textbox Code Example =[Driver_combo].[column](n)

Everything was working as it should when I was putting it together and saved
it. The next day when I opened it up, all of the autopopulate textboxes
displayed #Name? error.

Your syntax is slightly wrong. Try =[Driver_combo].Column(n) instead.
'Column' is not a user variable name but an object property and should not be
enclosed in brackets. Remeber the column index is relative to zero.

Also I had a date field that used the ActiveX Calendar Control (mscal.ocx)
this too was working as it should the day before and now I get an Ambiguous
Name Detected error when I run the control.

An ambiguous name occurs when the same name is detected in more than one DLL
(OCX or whatever) and the system cannot determine which one you mean. Check
first the References list (accessed via the Tools menu from the VBA coding
window) and make sure you have not got alternate libraries selected.
Otherwise check that you have not defined a conflicting variable name in your
code.

Note you can use conflicting names as long as they are explicitly prefixed
by the library. For example with both ADO and DAO libraries selected
'Recordset' is ambiguous but 'DAO.Recordset' or 'ADODB.Recordset' are
explicit.

Rod

 

[Rod Plastow]

After a little more research, the ambiguous name message is most likely
generated because you have duplicate procedure names.

Rod