On naming the control the same as the controlsource it is bound to: Don't.
Either don't name the control at all or give it a name similar but not
identical to the controlsource.
If you're never using VBA then this may not matter, but Access is unhappy
when a code reference refers to something on a form, and that something
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=11200
could be either a field or a control. Many developers prefix control names
with things like "txt", "cbo", "lbo" to indicate text box, combo box, or
list box respectively. There are many systems Choose one and stick with
it.
But in general, having a control name with the same name as its control
source will eventually bring you grief.
Think in your own mind: If I refer to Me.BottomTaxLabel, am I referring to
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=11200
the field within my recordset or the control on my form? It matters. The
moment you type a character into the control, and until you save the record,
the control and the field hold different values. If you refer to
Me.txtBottomTaxLabel, there is no ambiguity.