A family of Microsoft relational database management systems designed for ease of use.
The relative number of rows in the two referenced tables is not relevant. Each row in a table which models a many-to-many relationship type between those tables must have values in each of the two columns which reference the primary keys of the two referenced tables. An example would be an OrderDetails table modelling a relationship type between Orders and Products tables. If the Orders table has 100 rows and the Products table has 50 rows, and each order is for three products, then the OrderDetails table would have 300 rows (100 x 3) in each of which the OrderID and ProductID values, in combination, must be distinct. Not all products need to be referenced of course, but all Orders normally would be referenced as an order for no products would make little sense.
If the above does not help in solving your problem post back with details of the real world entity types between which the 'junction' table is modelling a relationship type.