no worries.
JUST FYI, you can prevent this happening by using a naming convention that will prevent duplicate names.
the naming convention is like to use is to prefix the table name on the column:
members:
memberID
memberFname
membersLname
etc...
lostdogs:
lostdogCounty
lostdogState
lostdogGender
etc...
this way, looking at the column name, you know what table it belongs to without having to use the log hand:
table.column
and you also know you will never have a duplicate column name, so will never be able to encounter the ambiguous name error
