same field names for bound controls

[scratch]

is there any problem with fields in differnent tables that have a field name that's the same? My concern is the control source for a bound control. Access can keep track of this if a few of these similar field names are on the same form and bound?

scratch

 

[scratch]

Would this apply to renaming a pk as an fk in another as well? An example:

Customer Order Returns 'tables
CustmerID fkOrderCustomerID fkReturnsCustmerID

I personally like leaving the pk the same in all the tables that it's an fk in - it's just a lot easier to read and understand table relations. Unless access may screw up referencing the right one, I'k like to leave the pk as fk names alone. What's the best way to go?