T
Todd
Thanks for the help!!
--
Todd
--
Todd
M Skabialka said:That's interesting to know - I was just speaking from experience where
sometimes things just don't work and the error messages are cryptic, and
using the same field name became something I avoided like the plague.
Mich
John Spencer said:Ah, but you can AS LONG AS you fully reference the field in the function.
The following works with no problem for me (untested in versions before
Access 2000).
Signature Field: UCase([TABLE NAME].[Signature Field])
'====================================================
John Spencer
Access MVP 2002-2005, 2007-2009
The Hilltop Institute
University of Maryland Baltimore County
'====================================================
or
SignatureFieldUCase: UCase([Signature Field])
so you won't have a circular reference (or whatever it is called in
Access where a calculated field can't have the same name as an actual
field)
Mich
Thanks, Mich.... < groan > I've been spending way too much time with SQL
Server these days, and the idiosyncracies between the two keep
overlapping in my mind... SQL Server allows an alias to have same name as
a field in a source table/query.