When the Access wizard builds a form for you, ALL bound controls are given the Name of the RecordSource field they are bound to. So, if the field in the query is LastName, the control's name property will be created as LastName. The two names will be identical. This caused a certain amount of confusion in earlier versions of Access because there was occasional confusion regarding on whether you were referring to the table column or the control itself. The current version of Access is less easily confused but old habits die hard and so I rename all the controls (not necessarily in the samples I build though) to include prefixes. that means you can always tell when reading my code whether it is referring to the control or the bound field.
However, you CANNOT reuse a bound field name as the Name property of a control it is not bound to. So, if you have a field in the RecordSource named AmtPaid, that field might be bound to a control of the same name but you cannot have a control named AmtPaid that is bound to a calculated value or to a different RecordSource field such as WeeklySalary. People don't usually make this mistake initially, they tend to make it if they are making modifications to the form and decide to change the control named AmtPaid and bound to the field from the RecordSource named AmtPaid to a calculation such as =AmtPaid * 52. This looks like it should work but it doesn't since even though AmtPaid is part of the calculation, the control is no longer bound to the field named AmtPaid, the control is now unbound because it is calculated.