Official info on #name? and #Type! errors

[got_access:]]

Hi All,
I'm trying to find Microsoft's official descriptions of the errors one finds with calculated text box controls on a form.

The #Name? error - I believe can occur with two possible situations.
1) Where the record source for the form does not contain table/query field that is being called out in the textbox.
2) Where there is some kind of naming conflict between the textbox control and another field on the form.

The #Type! error - I believe has to do with a mismatch of datatype called out on the calculated text control box.

 

[theDBguy]

Hi. Right, I read them the same way, but don't have a handy reference at the moment. So, basically, #Name means there is something being referenced in the expression that Access cannot resolve. It could be a name of a table, field, or some other referenced object. And #Type would most likely be an error regarding a wrong type of object or value in the expression.

 

[Deleted member 147267]

And one of the reasons for not being able to resolve a reference is ambiguity. I'm not a betting guy, but I'd wager someone else's money that you had misspelled or just wrong name in mind. By ambiguity I mean that a variable or field name in an expression is the same name as the control. This often happens as a result of using wizards. If I use a form or report wizard (which is not often) unless I'm just experimenting I will always rename all of the controls because Access will name your textbox the same name as the field it's bound to. Same goes for subform containers - same name as subform. That's just asking for trouble IMHO.