Data entry on many to many is done as one to many, after all you can only enter one record at a time.
Say you had People and addresses, many people could be at one address, many p0eople could have several addresses
PersonID, PersonName
AddressID, Address
PersonID, AddressID
If you wanted to enter a new address against an existing person then you would
insert a new address record, get the id
insert a new link record with the personid
This effectivley reduces the link to a 1 - 1
If you wanted to show all the addresses a person had that's 1 to many just a join from persons to personaddresees to addresses where personID = ...
To show all the persons at an address
join Addresses to PersonAddresses to Persons where addressid = ..., again 1 to many
You could show all addresses of all persons who had at least one address in Kent which is a many to many, but it would be very unfriendly
The main reason for a linktable aside from normalisation is so you can have a person with 0 to many addresses and vice versa, without having acolumn in one table for each possible instance of address, which it restrictive, wasteful and damn messy.
The link table lets you implement as two one to manys.
Aggregate examples might be
Select PersonID, PersonName,Count() from Persons, Personaddresses
Where Persons.PersonID = PersonAddresses.PersonID
group by PersonID
or
Select PersonID, PersonName,Count() from Persons, Personaddresses, Addresses
Where Persons.PersonID = PersonAddresses.PersonID
and PersonAddresses.AddressID = Addresses.AddressID
and Addresses.Address Like '%Kent%'
group by PersonID
Hths